The EJB specification has gone through a transformation unlike any other in J2EE. It has evolved from the previous EJB 2.1 incarnation that many considered an overly heavy and difficult component model into a powerful and flexible 3.0 standard that is the buzz of the industry. Its ease of use and popular lightweight persistence model are setting it up to be the standard of choice for server components and persistence applications.
This session will introduce and explain the EJB 3.0 concepts and API’s and will present examples of how to use them. Container component topics will include using EJB annotations and XML, injection of resources, defining and using interceptors and life cycle listeners and designing for remote and local interface reuse.
The EJB Persistence API will also be discussed in detail and examples of using the EntityManager API, named and native queries, O/R mapping and inheritance hierarchies using EJB 3.0 entities will be explained. Sample code will be used to illustrate new EJB development practices and provide attendees with the confidence and skills to be able to develop their own EJB 3.0 applications.
Prerequisites: J2SE 5
The EJB 3.0 specification, with its huge advances in ease of development and its drastically simplified programming model, has been widely acclaimed and embraced as the next generation of server-side application component technology.
While application developers will want to write new applications using the EJB 3.0 standard, the fact remains that there are still large numbers of existing applications that have already been written using previous EJB versions and other technologies. These application developers can clearly continue to use the flavor of EJB that appeals to them, or the proprietary product they already have installed, but many will undoubtedly want to reap the benefits of the new EJB 3.0 API. Some may be wary, though, of what they perceive could be a system rewrite.
This session discusses the issues of migrating from previous EJB versions and other architectures, and how it can be achieved. We examine the options available and discuss why some are beneficial and others are less so. We will explore what such a system will end up looking like once it has been migrated, and provide examples that demonstrate the migration process.
Prerequisites: EJB, server-side component or object persistence experience
Mike Keith has 15 years of teaching, research and practical experience in object-based and object-oriented systems, specializing in object persistence. He specializes in distributed persistent object systems and has designed and implemented numerous persistent object systems for Fortune 100 corporations. He has been involved in EJB since its initial release through spec reviews and CMP implementation products. He is an architect for Oracle’s TopLink and OC4J Container products and has recently been engaged in helping architect Oracle’s EJB 3.0 implementation in OC4J. He is a frequent presenter at JavaOne and numerous other conferences. He is currently co-spec lead of EJB 3.0 (JSR 220) and also represents Oracle on the Java EE 5 expert group (JSR 244).