One of the key outcomes of Java EE 5 / EJB 3.0 was the introduction of the Java Persistence API. JPA is a new standard API for Java persistence and object/relational mapping that supports use in both Java EE and Java SE environments.
The purpose of Java Persistence 2.0 is to augment the Java Persistence API to include further features requested by the community.
This session will give you an up-to-the-minute glimpse into work in progress on Java Persistence 2.0, and will provide you with an opportunity for feedback on new directions.
Aspects to be discussed include the following:
Expanded modeling capabilities and object/relational mapping functionality, including support for collections of embedded objects, ordered lists, combinations of access types, greater flexibility in combining existing mapping options, etc.
Expanded query capabilities and additions to the Java Persistence query language
Standardization of additional contracts for entity detachment and merge, and persistence context management
Standardization of sets of "hints" for entity manager and query configuration
Expanded pluggability contracts for Java EE environments
Support for validation
Linda DeMichiel is a senior architect in the Java EE Platform group at Sun Microsystems and the chief architect for Enterprise JavaBeans 3.0 and the Java Persistence API. As the Specification Lead for JSR-220, she was responsible for launching and leading the initiatives for Enterprise JavaBeans 3.0 and the Java Persistence API under the Java Community Process.
She has over 20 years of experience in the areas of databases, object persistence, distributed computing, and OO in both industry and research. Before assuming responsibility for EJB, she led the team that implemented Sun's first object/relational persistence product, and worked earlier at IBM on object/relational extensions to both DB2 and the SQL99 standard. She holds a Ph.D. in Computer Science from Stanford University.
Advanced Topics in JPA— In this talk we will introduce a few of the common features and use them as a platform on which we can discuss some of the higher order JPA topics. As part of this discussion we will show how to use multiple persistence units, define and tune identifier generators, create and invoke native queries, and use XML mapping files for overriding annotation metadata. We will also show how JPA can be used in Java SE and Spring environments.
Writing JPA applications— In this session Patrick explores the new Java Persistence API, and examine some common practices for how to write Spring applications that use JPA. Patrick will focus more on API usage than on mapping configuration, and will look at the bootstrapping and runtime behavior of JPA applications. You will learn about JPA's optimistic locking semantics, including the benefits of optimistic read locks. Patrick looks at when it's appropriate to use the different facilities of the Java Persistence Query Language (JPQL), and also discusses common extensions to the spec, including performance caching, pessimistic locking, and fetch strategies.
Java EE 5 Blueprints (JPA)— The Java BluePrints projects presents the programming model, guidelines and examples for designing enterprise quality applications and web services using Java technologies. Some of the areas covered are Ajax-enabled Web 2.0 applications, Persistence, JavaServer Faces, SOA with BPEL, and WS-Security. This talk will focus on the Java Persistence API.
Enterprise Development with JPA— Standardization of persistence inside of the Java EE platform, as well as in the SE environment, will finally provide enterprise applications with the ability to write to one API and be able to run on the vendor of their choice. This talk covers best practices and common usage patterns of the Java Persistence API in conjunction with a Java EE application server.
Using the Java Persistence API— Standardization of persistence inside of the Java EE platform, as well as in the SE environment, will finally provide enterprise applications with the ability to write to one API and be able to run on the vendor of their choice.
