It's clear that we are headed for continued change in enterprise Java. Business requirements are changing, with the rise of SOA and a richer web experience. Scripting languages and productivity frameworks such as Ruby on Rails are placing welcome pressure on enterprise Java to enable developers to deliver results quicker. The traditional application server seems less and less relevant in today's environment--especially as transformational technologies such as OSGi move to center stage.
In this keynote, Rod Johnson will consider where tomorrow's innovation will come from in enterprise Java. How will the role of the JCP change? Will other standards bodies play a role? Will end users be more empowered-and how can you help to shape the future? How will the continued rise of open source affect the platform-especially with Sun's recent embrace of open source, and the emergence of a significant and sustainable open source industry?
Rod Johnson has served as the President and CEO of SpringSource since inception and has over 12 years of technology and management experience. Rod conceived of and initiated the development of Spring. The Spring Porfolio of open source projects was based on the code published with Rod's best-selling Expert One-on-One J2EE Design and Development (2002). This book was one of the most influential books ever published on J2EE and the sequel, J2EE without EJB (July 2004, with Juergen Hoeller), has proven almost equally significant, establishing a comprehensive vision for lightweight, post-EJB J2EE development. Rod is one of the world's leading authorities on Java and J2EE development. He is a best-selling author and open source thought leader, as well as a popular conference speaker. Rod founded SpringSource and has been its CEO since inception. Rod has specialized in server-side Java since 1996 across a wide range of industries. Rods hands-on experience has led him to see problems from a client's perspective as well as a technology perspective, and has driven his influential criticism of bloated, inefficient, orthodox approaches to J2EE architecture. Rod regularly speaks at conferences internationally and continues to be actively involved in guiding the direction of Spring. Rod holds a BA with Honors in Computer Science, Mathematics and Musicology as well as a Phd from the University of Sydney.
Seam in Action - Part 2— In the second half of this session Peter Hilton and Nicolas Leroux explain why they chose Seam over the many competing frameworks, what it was like getting started with Seam, what its learning curve is like, and what their practical experiences with Seam has been on two commercial projects during the last year.
Seam in Action - Part 1— In the first half of this session, Pete Muir will introduce Seam, its contextual programming model and its tight integration with other frameworks such as Hibernate, jBPM and RichFaces. In the second half of this session Peter Hilton and Nicolas Leroux explain why they chose Seam over the many competing frameworks, what it was like getting started with Seam, what its learning curve is like, and what their practical experiences with Seam has been on two commercial projects during the last year.
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.
