Java EE 5/6 inverted not only the dependencies, but also some patterns and best practices as well. What are the best practices, how many patterns are needed and which patterns became anti-patterns? This workshop examines these topics and suggests some pragmatic and lean approaches.

Java EE 6 is a revolution, not an evolution. It fully changed the programming model and drastically simplified the development of enterprise software. The combination of technologies from Java SE (annotations, generics, enums), with reasonable conventions and Dependency Injection enables new idioms, approaches and makes the realization of ultra-lean applications possible. Some well known and already established J2EE best practices, however, became superflous or need some serious refactoring. This workshop discusses the classic J2EE patterns, and pre-assumptions, necessary rethinking with many code samples each targeting specific issues. Further more questions like:

• Are DAOs a best practice?
• Dealing with Wicket, JSF and GWT …and a single backend.
• Which presentation tier pattern do we still need?
• Are anemic JPA-entities a best practice?
• Are XML deployment descriptors legacy?
• Are EJBs lightweight?
• How to test EJBs?
• Is layering always a best practice?
• Do we still need factories?
• How to integrate with RESTFul services? Whats about SOAP?
• When to deploy EJBs into a ...WAR?
• -Are "Plain Old Web Containers" still interesting in the age of OSGI?
• Services or Objects - what is the way to go?

Especially the service oriented patterns and best practices will be directly compared with domain driven approaches and the impact of each to the efficiency of development and maintenance.