Enterprise Development with JPA (part 2)

1.	Intro
2.	Agenda
3.	Access Type
4.	Use FIELD access
5.	Inheritance
6.	Mapped Superclass
7.	Abstract Entity
8.	Inheritance Mapping
9.	Object Model
10.	Data Models
11.	Persistence Unit
12.	Example
13.	Persistence Contexts - 1
14.	Persistence Contexts - 2
15.	Persistence Contexts - 3
16.	PC Propagation
17.	Entity Caching
18.	Advanced Caching - 1
19.	Advanced Caching - 2
20.	Detaching Entities
21.	Detached Entities
22.	Transactions
23.	Optimistic Locking
24.	Configuration
25.	Component Packaging - 1
26.	Component Packaging - 2
27.	Adding the Entities - 1
28.	Adding the Entities - 2
29.	Adding the Entities - 3
30.	Adding the Entities - 4
31.	Adding the Entities - 5
32.	Adding the Entities - 6
33.	Packaging Options - 1
34.	Packaging Options - 2
35.	Packaging Options - 3
36.	Packaging Options - 4
37.	More Information

The recently-released EJB 3.0 specification has perhaps been one of the most talked-about technologies that has emerged from JCP for some time. At the centre of attention is the Java Persistence API, a lightweight persistence model that acts as a point of convergence for the dominant persistence products currently on the market.

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.

Some of the topics discussed in this talk:

• Enterprise entity models
• EntityManagers and persistence context propagation
• Entity caching
• Detaching and merging entities
• Entities in enterprise transactions
• Packaging and deploying

We will address the following common design questions:

• Should I use field or property access type?
• How often should I detach / merge?
• What sorts of restrictions should I follow when I design my entity object model?
• Can I put behavior in my entities?
• What transactional guarantees can I rely on?

Mike Keith is the co-specification lead of EJB 3.0 (JSR 220) and a member of the Java EE 5 expert group (JSR 244). He has 15 years of teaching, research and practical experience in object-oriented and distributed systems, specializing in object persistence. His expertise has stemmed from designing and implementing numerous persistent object systems for Fortune 100 corporations. He has been involved in EJB since its initial release and other forms of persistence since long before EJB. He is an architect for Oracle TopLink and the Oracle OC4J Java EE Container and is a popular speaker at numerous conferences and events. Mike co-authored the book "Pro EJB 3: Java Persistence API".

Patrick Linskey has been working with O/R mapping for over six years. He is an active member of both the JDO 2.0 and EJB 3.0 expert groups, and is on the JAOO Conference Program Committee.

As the founder and CTO of SolarMetric, Patrick drove the technical direction of the company. Now at BEA, he leads the EJB team in designing and implementation of the WebLogic Server EJB solution.

He has been the face of standards-based persistence, having evangelized JDO and EJB Persistence in hundreds of talks throughout the world. Under Patrick's leadership, Kodo has become the market leading JDO implementation with over 350 customers throughout the world spanning all industries, and is now the basis for the WebLogic Server EJB persistence provider.