The announcement of the Java Persistence Platform Project in Eclipse signals the inauguration of a new generation of persistence where all of the dominant persistence standards are implemented and accessible from a single source. The project, nicknamed EclipseLink, is composed of a set of separate runtime components that run in both clients and servers, and is the first open source project to offer a full suite of persistence technologies. By supporting all of the popular standards, including object-relational mapping using the Java Persistence API (JPA), object-to-XML mapping through the Java API for XML Binding (JAXB), and loosely bound Service Data Objects (SDO) that bridge the relational and XML worlds, EclipseLink is the most comprehensive persistence platform available. Equally compelling is the fact that these technologies are offered with a rich array of feature extensions and high-end performance options.
Attendees will learn what EclipseLink is, the standard technologies it implements, and how these technologies can be used separately or together to meet advanced and diverse application requirements. We will show examples of how to use EclipseLink to map Java objects in object-relational and object-XML contexts, and how it can be used in any runtime environment, including Java SE, Java EE, Spring and Tomcat.
Eclipse has lived most of its life as an IDE, and most will agree that it has achieved a great deal of success along the way. However, Eclipse is now all grown up and has decided to establish itself in runtime-land as well. Counted in its runtime component arsenal is its Equinox OSGi layer, its Rich Client Platform (RCP) API, and now a full Java Persistence Platform that includes a deluxe Java Persistence API (JPA) implementation. In this talk we will learn how to use the Eclipse JPA runtime layer both inside and outside Eclipse. We will see how the Eclipse Dali tooling assists in developing a JPA application, and also see what configuration metadata might be needed to get the application running. As part of the discussion we will examine the difference between writing applications targeted for a full Java EE 5 container and those built to run in a standalone Java SE environment.
Attendees are not required to have experience with JPA, but having some kind of Java persistence knowledge or object-relational mapping experience will help.
© 1997 2008 Kovsky Conference Productions Inc.; All rights reserved.