This session will walk the audience through the steps necessary to begin using the Seam framework (Web Beans - JSR 299). It will begin with a brief introduction to Java EE 5 through review of an existing JSF / EJB 3.0 application. We will then convert that application to one which uses the Seam framework, ultimately eliminating the need for the JSF managed bean. We'll also take advantage of the Hibernate validator framework (a component of Seam), allowing us to eliminate the JSF validators. Finally, we'll demonstrate Seam's portability by running the application on both JBoss and GlassFish.
Brian Leonard works as a senior software engineer with Sun Microsystems. He's been working with application servers before there was a J2EE standard, helping develop applications as well as the servers that run them. Until most recently, Brian's been focused on helping large enterprises implement and deploy highly-available architectures. In his current role, Brian is an evangelist for the Sun's Java development tools.
Large scale development of enterprise java solutions— You will get some insights into the development process at the NetWeaver Product Technology Unit and SAP applications build on top of the NetWeaver platform. We will share how we build large scale enterprise java solutions at SAP.
Java persistence - a Heretic's demonstration— The Java world is a thriving 'think tank' where the future of computing is created, a place of open-minded exploration. Nevertheless, there are taboos that the Java world seems reluctant to address. Weakly typed languages was one that has been confronted only recently, with JSR223. Object-oriented databases attract a lot of sympathy and precious little support. Everything that would stray too far away from the 'canon' of Java and JavaEE is, in reality, often considered with suspicion.
Guice— Put simply, Guice alleviates the need for factories and the use of new in your Java code. Think of Guice's @Inject as the new new. You will still need to write factories in some cases, but your code will not depend directly on them. Your code will be easier to change, unit test and reuse in other contexts.
JSR 303 - Bean Validation— Validating data is a common task that is copied in many different layers of an application, from the presentation tier to the persistence layer. Many times the exact same validations will have to be implemented in each separate validation framework, proving time consuming and error-prone. To prevent having to re-implement these validations at each layer, many developers will bundle validations directly into their classes, cluttering them with copied validation code that is, in fact, meta-data about the class itself.
Leading Open Source Middleware in Action— OW2 Members present and demonstrate leading OW2 projects working together to provide a full-featured open source information system based on Exo, XWiki, Bonita, JOnAS, SpagoBI, Talend, PEtALS, Orchestra and Spegic.
