Speaker- Debu has more than 14 years of experience in the IT industry and has published articles in several magazines and has presented at many conferences. He is a Senior Principal Product Manager of the Oracle Application Server development team. He is co -author of EJB 3.0 In Action.
Session Abstract
EJB 3 and the Spring framework are often cast as bitter contenders. Ever wondered if using both technologies together might make sense? If so, this session is worth your while. This session examines the scenarios where EJB 3-Spring integration will allow you to take advantage of the strengths of both technologies.
This session will cover the integration case for persistence, but also span across the complete feature stack of both technologies in search of great matches. Issues of usability, dependency injection, state management, web services, AOP are all carefully dissected. Integration scenarios and solutions are explored using practical, road-ready code samples.
The goal of this session is to give the attendee a clear and comprehensive picture of the case for interoperability between EJB 3 and the Spring framework. For users that do find compelling integration cases, the session outlines solutions.
The point-by-point analysis will be culminated in a comparison matrix that indicates cases where integration makes sense given a particular application development path. The session will then outline the techniques that can be used to accomplish seamless integration using existing as well as emerging technologies.
Copyright 2004 to 2008 Rightrix Solutions. All rights reserved. All product names are trademarks of their respective companies. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Rightrix Solutions and IndicThreads.com are independent of Sun Microsystems, Inc.
Views expressed at IndicThreads.com reflect the views of the authors alone, and do not necessarily reflect those of IndicThreads.com. IndicThreads.com and it's authors are not responsible for reader comments and opinions.