Lembro que no Conaphp de 2008 surgiu uma discussão forte sobre o MVC. Quais os papeis do model, do view, do controller, etc. Acontece que dependendo da região e da cultura dos programadores, os conceitos variam.

Tem gente que coloca regra de negócio no controller, tem gente que coloca script de validação no model… Não há meios de julgar o que é certo e o que é errado, pois todas as normas (inclusive as oficiais ultra secretas – leiam-se caras pra burro – ABNT, IEEE e cia) são seguidas somente pelos profissionais que DESEJAM segui-las.

Eu penso que você deve dançar conforme a música. Se você trabalha numa empresa que segue normas rígidas, que obriga você a ler, aprender e seguir essas normas determinadas, veja essas normas como boas práticas que vão garantir com que seu trabalho não pereça após a implementação e que alguma outra pessoa vai poder realizar manutenção e adicionar novas funcionalidades ao seu sistema no futuro. Sem contar a iminente possibilidade de você ser demitido por insubordinação, desorganização e outros…

Porém, academicamente falando, um padrão mínimo deve ser seguido.

Quando se trabalha com Zend Framework, por exemplo, segue-se a seguinte referência, sem direito a discussão:

• Model – Esta é a parte de seu aplicativo que define sua funcionalidade básica através de abstrações. Rotinas de acesso aos dados e regras de negócio poderão ser definidas aqui.
• View – Views definem exatamente o que será apresentado ao usuário. Geralmente os controllers fornecem dados para que cada visão possa renderizar de forma humanamente inteligível àqueles que utilizam o sistema. Views irão frequentemente obter dados do usuário. Normalmente é aqui que você irá encontrar código HTML nos seus aplciativos MVC.
• Controller – Controllers são responsáveis por manter a unidade do conjunto. Eles manipulam models, decidem qual view será apresentada para o usuário e, entre outros fatores, fornecem os dados necessários ao view para a renderização da tela dinâmica que será apresentada. Também repassam responsabilidades para outros controllers em algumas situações específicas. A maioria dos experts em MVC recomendam que os controllers sejam mantidos o mais enxuto possível.

Obviamente, há muito mais a ser dito sobre esse padrão, porém essa pouca informação já é suficiente para que qualquer desenvolvedor possa ter uma noção básica sobre a teoria do MVC no desenvolvimento de aplicativos.

O aprendizado por trás disso diz que tudo é relativo. Que os conceitos variam de um lugar para outro, porém diz também que você DEVE seguir as normas, sejam elas quais forem, quando for desenvolver utilizando o padrão MVC.

um abraço,

Diogo Besson

The idea of literacy development as the responsibility of all teachers, one of the core features of the curriculum reform in Scotland, is a challenging one for many secondary English and non-English specialists alike. While the perception of the English department as a service industry for the rest of the school, ensuring that young people are proficient in reading, writing, grammar and spelling, is almost a thing of the past, for some English teachers the thought of other subject specialists ‘teaching’ language skills is a threat to their own professionalism and perhaps even a dereliction of duty. At the same time, while many non-English specialists had happily embraced their role in the development of literacy long before the birth of Curriculum for Excellence, many others are reluctant to accept the responsibility, believing it to be somebody else’s job.

The language of the science outcomes demands sophisticated literacy skills

Arguably, the tensions described above were an inevitable consequence of the decision to maintain, more or less, the curriculum areas which existed before the review and, broadly speaking, the same departmental structures, to the extent that not even the nomenclature was up for debate – how relevant for example is the title ‘Home Economics’  for an area of study which is actually more relevant than ever in terms of healthy eating and wellbeing, but has a title which is not only years but decades out of date? Likewise Religious and Moral Education, which certainly needs to drop the ‘R’ word, and probably the ‘M’ word as well if it is to be taken seriously, since surely it is in fact Philosophy if it is being done properly.                

The same  is true to a great extent of English and English teaching. As someone who was proud to describe himself as an English teacher for many years, I was never entirely clear about my role, and I’m not sure that anyone else was either, the title itself suggesting …well, everything under the sun really. Was I teaching literature, or language, or media studies, or grammar, or spelling, or handwriting, or theatre?  The answer of course was all of them, and more or less in the order of priority which suited me and not the learners. It was great fun but somehow lacking in focus.

Unfortunately, the opportunity to rectify this confusion has been missed this time around, or perhaps was seen as a step too far; so instead we have two separate frameworks, Literacy and English as well as Literacy across Learning, which leads anyone outside of the educational establishment, and even some of those inside it, to the conclusion that there are literacy skills taught by English teachers and another, possibly less important, kind of literacy which is the responsibility of everyone else. (In actual fact the additional responsibility English teachers have is for the the study of literature, which is a separate matter).

This continued separation of roles is an artificial construct, and is not helpful. However, when you look at the language of the outcomes for all curriculum areas, the responsibilities seem clear enough. If I am a science teacher, for example, and a third level outcome for a learner in science says “I can produce a reasoned argument on the likelihood of life existing elsewhere in the universe” that would suggest to me that I have a responsibility not only to provide opportunities for that to happen, nor even simply to assess the extent to which the learner is able to do it, but to teach the skills required to produce a reasoned argument (which might include research skills; the ability to distinguish between fact and opinion; notetaking; summary; editing; presentation skills; dealing with feedback and many others). If I feel unable to do that at the moment, there is a definite and specific training need, and it is one which should be addressed as a matter of urgency. Unless, of course, your understanding of the responsibilities is different from mine.

Here’s a rough demo of my latest flash video player:

The MyLiveSession Demo

Currently using old video files and images from the good old MLS days…better assets make it look a lot nicer!

In this setup i’m streaming .flv via rtmp from Flash Media Server; When i get time i’ll add some demos showing custom (psuedo stream) and progressive .flv plus a demo of the windows media overlay to handle .mpg, .mp4 and .wmv files via http all within the same UI.

I’d love to know how the preview function works for you – you can activate it by hovering your mouse over the prev/next buttons, just wait 5 seconds and the image shown will change to a video of the next stream, audio will switch as well (NOTE: some of the videos currently avaialble dont have audio for a few seconds once they start – so it’s not so obvious). When both stream are playing what is the performance on your computer like, acceptable??

Feedback and suggestions appreciated, cheers.

In my recent post about “Layers” and “Patterns”, I was trying to argue the importance of “Services” and their role (as not the only player) in an SOA.  With that said, I am being reminded of a diagram I used to see describing Enterprise Architecture Frameworks by decomposing an organization into “Layers”.

Wikipedia currently is showing this image:

I believe the intent was two-fold. (1) Identify specific roles and domains and (2) show respective hierarchy to one another.  The latter may be more subtle, but clearly it is important for architects to understand the Business artifacts come first, then the data, then applications, then technology so why not stack them like the diagram suggests.  However, I was wondering why the triangle was chosen?  By using this representation, it seems to typify another generalization, albeit maybe unintended.  The domains on top are smaller then those on the bottom.  Was this on purpose?

I am pontificating now, but is this because we think we need to put more effort in terms of output for those with larger area?  Is this true and if so why not more outcry from the business?  Or maybe we all realize that in practice we see our architectures made up of more from the bottom then the top?  If nothing else, even today I see more energy, more conversation, more debate and more specialization in the technology space then any other domain of Enterprise Architecture.  Is this age-old symbolization of architecture the genesis of unintended consequences: Technology is King and the business is it’s humble servant?  How can that be, the business is at the top right?!?  Well maybe better said, Technology is King and the business is it’s diadem.

Consider flipping the triangle.  Where not only is the business at the top but also consumes the most area.  Then follows data, applications and technology where the bottom is smallest portion of the architecture.  I know this would never fly due to experts smarter than I saying, “It all points to technology and thus counterintuitive” or my favorite, “It does not have a flat foundation, how can it stand?”  Even so, I believe there is some merit in this new depiction.

With the advent of SOA traction in Enterprise Architecture, it should ideally minimize the importance, effort, and landscape of technology.  In a very real sense, technology is merely the interface gateway and maybe infrastructure to the enterprise.  The process modeling, data management, decision intelligence, service components should begin to be extracted from the technology space and become more common place in the business domain.  BPMN, BPEL, rules engines, process improvement and the like are forcing us to get the business people more involved in architecture – the true allure to an SOA.

And since I am busting down some long-standing doors, why not even change the domains slightly.  Why do we even need to bring up Applications anymore?  In the past we modeled our business after COTS or IT limitations, so the application domain is where the real business logic resided.  This lead to it being recognized as it own domain.  Now we realize we should model our architecture, systems, technology after our business.  Allow agility to enable technology to meet the individual need.  In this sense, the application domain has become a Service Layer.  Business oriented services that interact with applications, data or people.  I would still agree that the data domain trumps the service domain in both significance and effort thus higher on the diagram.  Finally that leaves the business at the top that is most important as well most invested in.  The business thus leverages data, services and technology to build the very processes and methodologies that model their goals, motivations, differentiations, etc.

My new diagram would look like this:

Eine Überblick bzw. Zusammenfassung von mir über das Thema was euch hoffentlich weiterhelfen wird.

Häwdtfan

Beschreibung

Ein Framework ist selbst noch kein fertiges Programm, sondern stellt den Rahmen
innerhalb dessen der Designer/Developer eine Anwendung erstellt zur Verfügung.

Ein Framework ist eine Reihe von Werkzeugen, Bibliotheken und Best Practices, die uns versuchen Arbeit abzunehmen.Wie? In denn man Routinenaufgaben in generische Module wiederverwendet kann.

• Ein Layout-Framework ist somit ein Arbeitswerkzeug zur Layouterstellung.
• Ein Universelles Layoutkonzept mit vielfältige Variationsmöglichkeiten.
• Eine vorgefertigtes „Gerüst“.
• Ein Arbeitswerkzeug zur Layouterstellung.
• Ein Framework gibt somit in der Regel die Anwendungsarchitektur vor.
• Ein Framework nimmt uns Arbeit ab indem Standardtasks vordefiniert sind.
• Frameworks helfen uns effizient und schnell ans Ziel zu kommen
  (Daher Kostenvorteile was auch an den Kunden weitergegeben wird. )
• Konzetration auf das Wesentliche!

Ziel

Das Ziel ist es, dass der Designer auf Aufgaben, die einzigartig für ein bestimmtes Projekt sich konzentrieren kann, anstatt das Rad jedes Mal neu zu erfinden in denn man Werkzeuge noch mal verwendet.

Produktivitätssteigerung!

Methoden, Arten von Frameworks

• Grid Frameworks (Anwendungsorientierte Baukästen, Grid- Basiertes Layout)
  • Layouterstellung mit HTML
  • Vordefinierte Gridklassen

• CSS Frameworks (Entwicklerorientierte Baukästen, Spaltenbasiertes Layout)
  • Vordefinierter Markup
  • Layouterstellung mit CSS

Beispiele dafür? (Werden nicht alle benannt!)

Grid Frameworks

• Blueprint CSS
• 960.gs
• YUI

CSS Frameworks

• Yaml
• A CSS Framework

Unterschiede

An der Stelle muss ich sagen dass es wirklich besser ist wenn ihr euch die Frameworks runterladet und die selber testet z.B. Yaml Builder und 960.gs. Ich persönlich finde diesen Weg als den besten weil so könnt ihr selber den Unterschied sehen und auch merken in denn man es ausprobiert 

Grid Frameworks

• Vordefinierte Gridklassen
• Layouterstellung mit HTML

CSS Frameworks

• Vordefinierte Markup
• Layouterstellung mit CSS

Beim Frameworks handelt es sich nun um Stylesheets mit einer Auswahl fertiger Klassen für diverse Spaltenraster im eigentlichen Inhaltsbereich einer Webseite.

Inhalte

Mögliche Inhalte bzw. Stylesheets  eines Frameworks:

• Reset.css
• Base.css
• Typography.css
• Layout.css
• Browser.css
• Table.css
• Form.css
• Print.css

„ Yaml liefert zusätzlich die vom Benutzer erstellte Struktur mit. (Html Code)“

Vorteile und Nachteile

Vorteile

• Tabellenfrei (CSS)
• Schnelle Entwicklung, Schnelle Ergebnisse
• Cross-Browser Kompatibilität (IE Bugfixes, Bugprävetion)
• Einheitliche Code Basis
• Normalisierung der Code
• Einhaltung von Standards
• Vermeiden von alltäglichen Fehlern
• Steigerung der Produktivität
• Verbesserter Workflow bei Team-Arbeit
• Flexible und Pflegeleicht
• Modulare Aufbau
• Wohl geformten Markup

Nachteile

• Einarbeitungszeit für das Framework
• Frameworks erzeugen mehr Code als notwendig (Overhead)
• Eigenschränkte Kreativität durch Vorgaben (Individuelle Layouts brauchen individuelle Lösungen);-)

When one decides to consider “Going Green”, or looking at “Sustainable Practices”, it can quickly become very confusing.

There is so much information out there that it can become overwhelming. But relax; there are some scientific frameworks that can help you to achieve your sustainability goals, while at the same time considering your short-term and long-term business or community objectives.

The three frameworks that I will address here are: The Triple Bottom Line, Zero Waste, and The Natural Step.

The Triple Bottom Line is pretty straight forward. In decision making, one must consider the People, the Profits, and the Planet. According to our now mainstream Wikipedia, The Triple Bottom Line is made up of ‘Social, Economic, and Environmental’ capital, or the ‘People, Planet, and Profits’.  The People are referred to as the “Human Capital”.  The Planet is referred to as the “Natural Capital”. And the Profits are referred to as the “Economic Capital”. All must remain in proper balance for long-term sustainability.

Zero Waste is a philosophy that encourages the redesign of resource use so that all products are reused or recycled. This is an “Upstream Philosophy”. Zero Waste is a philosophy that combines the elements of resource utilization and product or service design with a focus on the entire life cycle of the product or service. The focus throughout is:

• minimizing virgin resource utilization
• maximizing reuse and recycled resources, service or product delivery with minimal environmental impact
• and end-of-life de-construction resulting in materials that can be reused or recycled through composting or inorganic technical closed-loop cycles

Zero Waste requires design forethought upstream, during product planning, so that resource recovery, recycling and composting downstream can occur with minimal or no waste to bury or burn.

The Natural Step is based on 4 Systems Conditions.

System Condition 1:  In a Sustainable society, nature is not subject to systematically increasing concentrations of substances extracted from earth’s crust.

System Condition 2: In a sustainable society, nature is not subject to systematically increasing concentrations of substances produced by society.

System Condition 3: In a sustainable society, nature is not subject to systematically increasing degradation by physical means.

System Condition 4; In a sustainable society, people are not subject to conditions that systematically undermine their capacity to meet their needs.

Working with The Natural Step, each organization or community must draw its own conclusions from these basic principles. In the Natural Step Framework, we utilize a four-step “ABCD process” to provide a systematic way of “backcasting from principles” into practice, for sustainability planning and decision-making. The ABCD process really is the glue that holds The Natural Step Framework together. This framework can help us sort through the complexity and data by revealing patterns and relationships, so that we can make sense of all the information and help you to move forward in a strategic fashion.

Playing with HYPE some more this time comparing the difference between calling ComputeSpectrum() direct and via SoundAnalyzer.

SoundAnalyzer is currently using the getFrequencyIndex() method which should spread the ByteArray data psychoacoustically based on Brandens’ previously collated values. See the Hype Blog Post – Understanding…

I’m using 2 different apps/UIs so the display is not identical but the way the data is drawn is! Also don’t run 2 files at the same time as each will display the combined data – that’s a SoundMixer issue, naughty!

Check out these examples:

• Sweep No Hype
• Sweep Hyped Up
• Audio File (Heavy) No Hype
• Audio File (Heavy) Hyped Up
• Audio File (Soft) No Hype
• Audio File (Soft) Hyped Up

NOTE: There seems to be an issue with the ‘no hype’ files – returning an end of file error, seems to be an issue with FMS especially if other flash apps are running in other matching browser tabs/windows. If you see it check what else is running flash, close it and refresh your browser – it should go eventually… sorry!

When i get time i’ll test the other methods getOctave() and getFrequencyRange().

A couple of experiments using HYPE.

Hype is great! I’ve been staring at these just tweaking them slightly over and over again – so many permutations it’s very possible the really good ones got lost in the process…

The Word Is
No End In Sight

Mais uma IDE de programação para a linguagem Java, agora em português, com menos de 3Mb e feita por um brasileiro . O único defeito é que é para Windows . Seguem as informações abaixo. Informação retirada do site JavaFree.org.

Para quem nunca ouviu falar do MakeWare Java, o MakeWare Java é uma ferramenta de programação que eu desenvolvi para o desenvolvimento de aplicações usando a linguagem Java. Você pode fazer várias tipos de aplicações com essa ferramenta: Aplicações para console, aplicações gráficas com formulários (como no Delphi), aplicações baseadas em sistemas distribuídos, Applets Java,Aplicações para Banco de Dados e até aplicações para celulares, com o J2ME.

No MakeWare Java você possui sete tipos diferentes de projetos, são eles:

- Projeto Java Simples : Neste tipo de projeto você pode trabalhar com o essencial do Java: classes, interfaces e pacotes. E você pode Criar:

- aplicações baseadas em console e,
- aplicações gráficas utilizando componentes Swing

- Projeto Java RMI: Neste tipo de projeto, você cria um modelo pronto de sistema distrbuído Java utilizando RMI (Remote Method Invacation). Nele você vai especificar o cliente, servidor e interface remota. Para que você tenha um exemplo do seu funcionamento, retire os comentários existentes nos cliente, servidor e interface.

- Projeto Java Corba: Neste tipo de projeto, você cria um modelo pronto de sistema distrbuído Java utilizando Corba (Common Object Request Broker Architecture). Nele você vai especificar o cliente, servidor e interface (IDL). Para que você tenha um exemplo do seu funcionamento, retire os comentários existentes nos cliente, servidor e interface.

- Projeto Java Applet: Neste tipo de projeto você cria aplicações applets em Java, onde toda a execução será exebida no seu browser.

- Projeto Java Socket: Neste tipo de projeto, você cria um modelo pronto para trabalhar com Sockets. Nele você vai especificar o cliente e servidor. Para que você tenha um exemplo do seu funcionamento, simplesmente execute o projeto, não é preciso descomentar nada. O Projeto Java Socket já possui agora um help.

- Projetos Java BD: Neste projeto é criado um modelo pronto que faz a utilização de mecanismos de banco de dados fornecidos pela linguagem Java, o JDBC (Java DataBase Connectivity). Também nesse projeto podemos fazer uso e criar uma fonte de dados ODBC (Open DataBase Connectivity), que funciona como um “alias” para o nosso banco de dados. No momento, o projeto Java BD só cria fotne de dados voltados para banco de dados Accesss.

- Projeto Java Mobile: Este é um tipo de projeto voltado para o desenvolvimento de aplicações Java para dispositivos móveis (J2ME). Para usar esse projeto, é necessário ter instalado o o Wireless Tool Kit da Sun(de preferência na versão 2.5.2 (versão atual)) voltado para dispositivos do tipo CLDC (Connected Limited Device Configuration). Para fazer o download deste prgrama, clique aqui. A instalação do Wireless Tool Kit NÃO É OBRIGATÓRIA, caso você não esteja interessado em desenvolver aplicações para dispositivos móveis, não precisa informar o diretório.

Observações sobre o Projeto Java Mobile : Quando você cria um projeto Java Mobile, é criada também uma pasta com o mesmo nome do projeto, quando você mudar o projeto para um outro local, leve essa pasta junto.

O MakeWare Java oferece diversos recursos que facilitam a vida do programador, como um analisar dinânico de erros de código, mostrando em tempo de projeto onde se encontram os erros daquele e , dependendo do erro, ele te da uma sugestão para você corrigir aquele erro.

O MareWare Java ainda oferece alguns utilitários que ajudam o usuário no desenvolvimento de suas aplicações, são eles: Você conta com um utilitário que realiza consultas SQL em um determinado banco de dados Access, caso vá trabalhar com banco de dados em Java. Você também conta com um utiliário que cria, de modo fácil, arquivos JAR (Java Archive). Um arquivo JAR é como se fosse um arquivo ZIP que contém todas as classes e entre outros arquivos que constituem uma aplicação Java.

O MakeWare Java faz tudo isso com apenas 2,88MB.

Pré-requisitos:

Para o MakeWare Java, é preciso que você tenha instalado o JDK, de preferência da versão 5.0 em diante.

Se por acaso você deseja criar aplicações para celulares , é preciso que você tenha instalado o Wireless Tool Kit, versão 2.5.2.

Para fazer seu download, visitem:

http://makeware.orgfree.com/mkjava.php

De symfony bughuntday was een succes en net zoals de bughuntday van ZF was er ook een feestje in het station van Antwerpen-Centraal diezelfde avond (ik ging echter meteen naar huis). Ik ben rotsvast van overtuigd dat iedereen die aanwezig was, heel wat hebben bijgeleerd. Zeker ik had er wat aan, ook al had ik geen bugs op kunnen lossen en had ik op sommige momenten misschien net iets teveel geaarzeld. Daarnaast raak ook ik steeds meer vertrouwd met de community (phpbenelux), bestaande uit zeer vriendelijke mensen. Intussen heb ik wat beter kennis gemaakt met een paar van hen.

Het volgende event op vrijdag 20 november is het Cal Evans goodbye party. Met een locatie als Utrecht is de kans redelijk klein dat ik erbij kan zijn. Afwachten tot een goede event dan maar…

Olá,
acredito que você que está lendo este artigo deve se encaixar em pelo menos uma dessas opções:

• Me conhece e não sabe do que se trata esse tal de Oraculum Framework (uns 31%)
• Tomou conhecimento do projeto pela internet (uns 26%)
• Viu algum site ou outra coisa que foi desenvolvida com ele sem saber (uns 17%)
• Me conhece e viu eu criando alguma coisa com ele “ao vivo” (uns 4%)
• Acabou de cair neste ’site’ clicando em algum link (uns 22%)

Pois bem, talvez uns 38,73% que conhecem o projeto estejam (talvez felizes) pensando “Demorou pra acabar…”
E é por isso que criei este artigo com este título!

Este site ficou muito tempo sem atualização, e o projeto em si ficou “aparentemente” abandonado. Porém, neste tempo todo, estive trocando idéias com outras pessoas que optaram por criar frameworks e outras ferramentas de código aberto.
Isto foi necessário para ter uma ideia de quais caminhos o projeto deve tormar, para que seja útil não somente a um pequeno grupo de pessoas que optou por utilizá-lo, mas a outras pessoas também.

Com isto em mente, e focando em transformar o projeto em um framework mais maduro, optou-se por reescrever boa parte de sua estrutura, separando em partes que não serão apenas úteis ao Oraculum, e sim poderão se tornar úteis para outros projetos, ou até mesmo para uso individual, pensando especialmente em pessoas que talvez não queiram adotar o framework por completo.

Se quiser saber mais sobre o futuro do Oraculum entre em contato deixando um comentário, ou faça parte do nosso grupo…
http://groups.google.com.br/group/oraculum-dev

Quanto à possibilidade de o projeto acabar, pode esperar sentado

Algumas novidades devem ser divulgadas em breve

Abraço
Patrick Kaminski

This came to me as a surprise as I ignored this when I first saw it as a java platform thing. Recently, while going through some of the new Flash frameworks for fireworks and magic, it hit me again. And this time I made sure to check it out. To my surprise its a beast wrapped up in a beautiful wrapper. Having all the potentials of JAVA, Processing is a new kind of language(or may be Sripting language). Internally it compiles back to Java and can be used along with any front-end Java application. The real magic is its speed, and the fireworks it does. A very simple API and out of the box compilation support. It provides a lot of things out of the box,which is best for any newbe to Java platform. It comes with its own IDE,though one can choose to use Eclipse if she/he wants to. Compilation is instant and right upfront. When talking about packaging,it does nice job of compiling to all the platforms,Windows,Linux and Mac from Windows itself. The size of the compiled files(java applets) are as small as SWFs.

For a Flash developer this is a real option to try out Java this way. For the scripting Processing provides will make the Flash developer feel right at home. A lot of similarities All most everything is similar except for the APIs,which will make one think as if one is working in a Flash-platform framework. One gets animations, mouse actions and stage like behaviors from the application too

I would say, a must try for all the Flash and JAVA guys out there.

Happy flashing

I just discovered the play framework for java. I am embarrassed  to admit that it is complete news to me. I am curious to see how it holds up to the python frameworks I am looking at right now in terms of rapid development and ease of configuration.

I really hope it integrates nicely with IntelliJ IDEA, which I still consider the best IDE ever made.

There is no shortage of frameworks out there. The Information Technology Infrastructure Library (ITIL) comes from good old UK, in response to the growing dependence on IT starting in the ’80s.

5 ITIL Parts

1. Service Strategy includes, service value definition, business case development, service assets, market analysis, and service provider types.
2. Service Design includes, availability, capacity management,  IT service continuity,  information security, supplier management, and service catalog management.
3. Service Transition includes, Configuration Management, Testing, Release and deployment management, Change Management, and Knowledge Management.
4. Service Operation includes, technical management, application management, operations management and service desk.
5. Continual Service Improvement includes, measurement and reporting, and improvement.

Highlights

• ITIL is not for the mom-and-pop stores, as it’s quite expensive.
• Any organization interested will need training, but this applies to most comprehensive frameworks. Speaking of training, any framework training should include labs using real life use cases.

As with any framework, it’s important to understand the best practices it promotes and not blindly follow it to create deliverable. Unfortunately, frameworks often brings a lot of religious zeal  and ITIL is no exception. However, for a successful project, pragmatism is essential. No one framework will ever have all the answers. There’s only a handful of ways to do the right thing and it includes, Requirements Analysis, Design, Implementation, Test, and Deployment–regardless of what the framework calls them.

Lista com 10 bons plugins para a jQuery.

Clique aqui para ver a lista

Via JavascriptNews on Twitter

PUREENERGY312

SAMUEL DANIEL  LOVELESS – S.D.L. –  PUREENERGY312

 

“If you have the power to do something good; you have the responsibility to do it”

 Mr. William J Clinton

NETWEAVING FOR MY OWN BUSINESS

Bem, para quem for começar a estudar algum framework sobre a programação JAVA, aconselho que seja um framework conhecido e que possua uma boa documentação ensinando os passo que tenha que ser seguidos. Do contrário, se tornará uma missão quase impossível ou inviável.

Mas, vamos primeiro explicar o que seria Framework, e de acordo com (Oliveira, 2005) em seu artigo – O Universo dos Frameworks Java:

uma solução para um conjunto de problemas em comum, com uso de classes e interfaces, que disponibilizam objetos com capacidade de capturar funcionalidades comuns a várias aplicações.

Aquém estaram dispostos alguns frameworks que considero ser bons o bastante para qualquer aventureiro que deseje se enveredar, tendo em vista que os links em amostras nos nomes dos selecionados são oficializados, não limita que seja buscados outros, porém fica a critério e risco de cada que assim optar.

Frameworks sugeridos:

Struts – um dos mais usados em ambientes corporativos para construção de aplicações web. Usa o modelo MVC e caracterizado por uma camada de controle com uso de J2EE e XML (Oliveira, 2005).

JSF – JavaServe Faces – JavaServer (TM) Faces simplifica a criação de interfaces de usuário. Os desenvolvedores de vários níveis podem construir rapidamente aplicações web por: montagem de componentes reutilizáveis de interface do usuário em uma página, permitindo a conexão desses componentes com uma fonte de dados de aplicação e cliente fiação eventos gerados para o servidor-manipuladores de eventos secundários.(javaserverfaces: JavaServer Faces Community)

MyFaces – é uma implementação do JavaServer (TM) Faces (JSR 127), uma estrutura nova e futurística de aplicação web que exerce o MVC. Possui características e conceitos que estão além do Struts. (Open Source Web Frameworks in Java)

Tapestry – é um framework open-source para dinâmicos, robustos, e altamente escalável de criar aplicações web em Java. Tapestry complementa e reforça o padrão Java Servlet API, e assim que funciona em qualquer servlet container ou servidor de aplicação (Apache Tapestry – Welcome to Tapestry)

WebWork – é um web Java-framework de desenvolvimento de aplicativos. É construído especificamente com a produtividade do desenvolvedor e simplicidade de código em mente, oferecendo suporte robusto para a construção de modelos reutilizáveis de interface do usuário, tais como controles de formulário, temas IU, internacionalização, mapeamento dinâmico de parâmetros de formulário para JavaBeans, cliente robusto e validação do lado do servidor, e muito mais. (WebWork – WebWork)

Spring Framework – Spring aborda preocupações mais com a infra-estrutura de aplicações típicas. Vai a lugares que outros frameworks não vai. (The ServerSide – Enterprise Java Community)

Since probably from Tuesday I will be busy studying Spring and other technologies, I’d like to dive in a bit and see what are the foundations of this platform. Probably this topic will gain deepness with time, but now let’s start really simple and watch one feature that makes Spring different from EJB: the Inversion of Control pattern.

Imagine to have two classes, Door and Handle. The Door has a private variable that is its Handle, and when it is instantiated with new Door(), it will build a new Handle() inside its constructor as seen in the following diagram.

If we set up things in this way, there is a tight coupling between Door and Handle, and probably every change to the Handle class (for example, adding a parameter to the constructor) will affect even the Door class: to prevent this high coupling (class Door is responsible even for the creation of the Handle), we could have a IoC framework, that will have the responsibility to inject the instance of class Handle to the class Door, confining changes of class Door to the IoC framework. Class Door will only have a private variable Handle and a method setHandle(Handle h) to get the reference from the IoC framework.

In this case, class Door and Handle are independent, since the IoC framework uses the public method of class Door to set up the Handle.However, there are three different ways to implement the IoC pattern, and every web framework uses its implementation.

Setter-based IoC: like in the example I showed before, we use a setter method to inject the referred object (Handle) in the referring object (Door). In this way, even if Handles change a lot during its lifetime in the development, we prevent Doors from changing: the main drawback is that we expose the internal variables with setter methods, violating the key OO principle of classes, that is encapsulation of data.

Constructor-based IoC: we use a constructor to set the reference of the object, so that only the creator knows about the referenced object.

Interface-based IoC: objects have to implement a specific interface of the IoC framework, so that the framework will be able to properly inject the objects. In this way there is no need for an external configuration file with the objects’ references. This locks your application to a specific IoC framework.

I am sure this approach has a lot of advantages, most of all when you don’t know much about the referred class and how it will change in the application lifecycle, but i think that in order to fully understand its potential it should be seen in a well defined context, comparing the same web application written with EJB and with Spring that accompanies the IoC pattern with principles of Aspect Oriented Programming. Hope to learn this in the future.

Pattern-Oriented development is paramount in IT.  Patterns are used for designing software [POSA], integrating applications [EIP] or building enterprise systems [PEAA].  They make us feel comfortable that are our solution in the end will be extensible, reusable and hopefully along the way we managed avoiding some age-old pitfalls.

One thing enterprise software architecture teaches us is to rely on layers.  There are various patterns and styles of layers but more than likely if you are missing layers you are missing the mark with your framework.  Inside the context of integration landscapes and even application development, the introduction of “services” has greatly improved our ability to leverage layers well – make them more understandable, reusable and frankly standard.

Services & Layers

Services can mean lots of things, from a simple exposed interface to a data object, to an managed end-to-end business process, to an  interactive SOAP web service or EJB.  But at the end of the day, the term service has become common with the “stuff” or components we should be interacting within our layers.

If it’s a data layer, then provide me data-access CRUD like services.  If it’s a domain layer, provide me with business process logic.  If it’s an application layer, provide me with interface adaptors.  It it’s a presentation layer, provide me with representational views. And the list goes on and on, but we all agree we should be employing our patterns with services in mind in both development and discussion.

Does this therefore mean all architecture lends itself to Service-Oriented Architecture?  Well – no.  Service abstraction is something service-oriented architecture leverages but in practice an SOA is far more.  Furthermore, I contend that due to this lack of understanding, there is a very high risk of creating a “Service Architecture” (SA) and missing the boat all together on the sought after “Service-Oriented Architecture” (SOA).

Service Architecture

The SA is something we rarely talk about and only whispers can be heard of it in JAD meetings, or final production audits.  As a definition, I will give it this:  An Integration Landscape focusing on providing interoperability primarily through exposing and managing services across the enterprise.   In short, take your spaghetti code and stovepipe applications – re-architect them using services and layers (ignoring the true patterns from whence they came) – and you are left with an expensive replica of what you had: a point-to-point mess only this time with fancy service names attached to all those tightly-coupled interfaces.  And just because you decided to run all this on top of the latest “ESB” you hope to god the resultant SOA guarantees all the power it touts.  For this reason, I have grown to hate the term “integration point”.  As if all I need to do is define some necessary communication /action and provide some code to interoperate and “voila”, a true “service” comes out and now we are on our way to an SOA.  Sorry to say nope – designing integration landscapes by focusing on integration points, will usually get you quickly to a place where “web” and “point” are frowned upon.  (Referring the web chaos of point-to-point architectures).  Unless of course you were going for P2P, but since this BLOG is about SOA, I would assume you are not – and thus frowning is applicable.

Service-Oriented Architecture

SOA has evolved to mean so much, maybe too much, but at the least it is associated with a series of highly desired characteristics of enterprise application architecture.  Benefits like agility, governability, real-time, guaranteed, extensible and intelligent add to our ROI while benefits like reusability, maintainability, operational efficiency, automation, auditability reduce our TCO.  So how do we ensure we get all this?  Is it even possible?  Or is SOA another ivory tower pipe dream big software vendors and consultants are helping us peddle?

Check out some of my previous postings for definitions of an SOA – but in short, I would have preferred the “S” stood for Standard.  As in the tried and true standards that have really stood the test of time and now we finally are smart enough to realize it and start repeating it rather than conjuring up something new for our own ego sake.  However, for this posting I will offer this up for defining an SOA: An Integration Landscape that provides both interoperability and infrastructure through a strategic enterprise solution embodying connectivity, consolidation, composition and completeness.  Before I get hammered by the SOA for dummies people who say where is mention of the business people, this is meant to constrain SOA as an integration landscape not a project methodology.  I am not trying to redefine IT departments and IT business as we know it, just pointing out that when I look at what was actually implemented, how can I tell if it was more of an “SA” or “SOA”.  Besides, I added words like “enterprise” and consolidation to include the “business” (yes the stakeholders and business owners are important) – you cannot achieve consolidation or completeness without the business. See my blog on SOA Maturity.

The big deal here is the combination of technology, infrastructure (IT resources and Business resources where resources are people, processes and tangible assets) and standardization in a way that shows evolution and maturity of thought on both sides.  ESBs, web services, integration points, BPM or even technology patterns can not achieve this alone.  For an SOA to begin to produce all the benefits it so badly wants to, it needs some old school experience to pave the way.  Don’t throw out all your old PM methodologies or Architectural gurus in favor for new age hype.  Slow down, question why, document decisions points, make sure you are actually modeling your business not technology or a deadline, and for goodness sake, make sure the solution everyone is going for actually makes sense.

from “Hibernate in Action” -

Hibernate defines several lock modes:
■ LockMode.NONE—Don’t go to the database unless the object isn’t in either
cache.
■ LockMode.READ—Bypass both levels of the cache, and perform a version
check to verify that the object in memory is the same version that currently
exists in the database.
■ LockMode.UPDGRADE—Bypass both levels of the cache, do a version check
(if applicable), and obtain a database-level pessimistic upgrade lock, if
that is supported.
■ LockMode.UPDGRADE_NOWAIT—The same as UPGRADE, but use a SELECT…FOR
UPDATE NOWAIT on Oracle. This disables waiting for concurrent lock releases,
thus throwing a locking exception immediately if the lock can’t be obtained.
Understanding database transactions 167
■ LockMode.WRITE—Is obtained automatically when Hibernate has written to
a row in the current transaction (this is an internal mode; you can’t specify
it explicitly).
By default, load() and get() use LockMode.NONE. LockMode.READ is most useful with
Session.lock() and a detached object. For example:
Item item = … ;
Bid bid = new Bid();
item.addBid(bid);
…
Transaction tx = session.beginTransaction();
session.lock(item, LockMode.READ);
tx.commit();
This code performs a version check on the detached Item instance to verify that
the database row wasn’t updated by another transaction since it was retrieved,
before saving the new Bid by cascade (assuming that the association from Item to
Bid has cascading enabled).
By specifying an explicit LockMode other than LockMode.NONE, you force Hibernate
to bypass both levels of the cache and go all the way to the database.