JPA

1. JPA Java Persistence API

2. Introduction • The Java Persistence API provides an object/relational mapping facility for managing relational data in Java applications • Created as a part of EJB 3.0 within JSR 220 • Merger of expertise from TopLink, Hibernate, JDO, EJB vendors and individuals • Released in May 2006 as a part of Java EE 5 • Integration with Java EE web and EJB containers provides enterprise “ease of use” features • Can also be used in Java Standard Edition

3. Java Persistence • Java Persistence consists of three areas: • The Java Persistence API • The query language • Object/relational mapping metadata • Versions • JPA 1.0 (part of EJB 3.0, Java EE 5) • JSR 220:http://jcp.org/en/jsr/detail?id=220 • JPA 2.0 (part of EJB 3.1, Java EE 6) • JSR 318:http://jcp.org/en/jsr/detail?id=318

4. Reference implementations • JPA 1.0 reference implementation • TopLink Essentials by GlassFish project • javax.persistence package • open source (under CDDL license) https://glassfish.dev.java.net/javaee5/persistence/ • JPA 2.0 reference implementation • EclipseLink • http://www.eclipse.org/eclipselink/

5. Entities • An entity is a lightweight persistence domain object • Java class that typically represents a table in a relational database, instances correspond to rows • Requirements: • annotated with the javax.persistence.Entity annotation • public or protected, no-argument constructor • the class must not be declared final • no methods or persistent instance variables must be declared final

6. Requirements for Entities (cont.) • May be Serializable, but not required • Only needed if passed by value (in a remote call) • Entities may extend both entity and non-entity classes • Non-entity classes may extend entity classes • Persistent instance variables must be declared private, protected, or package-private • No required business/callback interfaces • Example: @Entity class Person{ . . . }

7. Persistent Fields and Properties • The persistent state of an entity can be accessed: • through the entity’s instance variables • through JavaBeans-style properties • Supported types: • primitive types, String, other serializable types, enumerated types • other entities and/or collections of entities • embeddable classes • All fields not annotated with @Transient or not marked as Java transient will be persisted to the data store!

8. Primary Keys in Entities • Each entity must have a unique object identifier (persistent identifier) • @Entity • public class Employee { • @Id private int id; • private String name; • private Date age; • public int getId() { return id; } • public void setId(int id) { this.id = id; } • . . . • } primary key

9. Persistent Identity • Identifier (id) in entity = primary key in database • Uniquely identifies entity in memory and in DB • Persistent identity types: • Simple id – single field/property @Id int id; • Compound id – multiple fields/properties @Id int id; @Id String name; • Embedded id – single field of PK class type @EmbeddedId EmployeePK id;

10. Identifier Generation • Identifiers can be generated in the database by specifying @GeneratedValue on the identifier • Four pre-defined generation strategies: • AUTO, IDENTITY, SEQUENCE, TABLE • Generators may pre-exist or be generated • Specifying strategy of AUTO indicates that the provider will choose a strategy @Id @GeneratedValue private int id;

11. Customizing the Entity Object • In most of the cases, the defaults are sufficient • By default the table name corresponds to the unqualified name of the class • Customization: • The defaults of columns can be customized using the @Column annotation @Entity(name = “FULLTIME_EMPLOYEE") public class Employee{ …… } @Id @Column(name = “EMPLOYEE_ID”, nullable = false) private String id; @Column(name = “FULL_NAME” nullable = true, length = 100) private String name;

12. Entity Relationships • There are four types of relationship multiplicities: • @OneToOne • @OneToMany • @ManyToOne • @ManyToMany • The direction of a relationship can be: • bidirectional – owning side and inverse side • unidirectional – owning side only • Owning side specifies the physical mapping • Inverse side is indicated by “mappedBy” attribute

13. OneToOne Mapping [1] Create unidirectional relationship from Singer to Person: @Entity @DiscriminatorValue("SINGER") publicclass Singer extends Artist{ @OneToOne private Person person; . . . } Result: In database “person_id” field is added to “artist” table, which contains foreign keys to “person” table

14. OneToOne Mapping [2] Make this relationship bidirectional: @Entity publicclass Person implements PersistentEntity { . . . @OneToOne(mappedBy="person") private Singer singerInfo; . . . }

15. @Entity @Id @ManyToOne ManyToOne Mapping public class Sale { int id; ... Customer cust; } } SALE ID CUST_ID . . . CUSTOMER ID . . .

16. @Entity @Id OneToMany Mapping public class Customer { int id; ... Set<Sale> sales; } CUSTOMER ID . . . @OneToMany(mappedBy=“cust”) public class Sale { int id; ... Customer cust; } @Entity SALE ID . . . CUST_ID @Id @ManyToOne

17. Additional notes “Many” end of the bidirectional ManyToOne relationship cannot be the inverse side of the relationship • @ManyToOne annotation cannot contain attribute “mappedBy”

18. General rules • If “One” end of the relationship is the owning side, then foreign key column is generated for this entity in database • If “Many” end of the relationship is the owning side (e.g. unidirectional ManyToOne or any kind of ManyToMany), then join table is generated

19. ManyToMany Mapping @Entity public class Customer { ... @ManyToMany @JoinTable( name="CUSTOMER_SALE", joinColumns=@JoinColumn( name="CUSTOMER_ID",referencedColumnName="customer_id"), inverseJoinColumns=@JoinColumn( name="SALE_ID", referencesColumnName="sale_id") Collection<Sale> sales; } @Entity public class Sale { ... @ManyToMany(mappedBy=“sales”) Collection<Customer> customers; }

20. Relation Attributes • CascadeType • ALL, PERSIST, MERGE, REMOVE, REFRESH • FetchType • LAZY, EAGER @ManyToMany( cascade = {CascadeType.PERSIST, CascadeType.MERGE}, fetch = FetchType.EAGER)

21. Entity Inheritance • An important capability of the JPA is its support for inheritance and polymorphism • Entities can inherit from other entities and from non-entities • The @Inheritance annotation identifies a mapping strategy: • SINGLE_TABLE • JOINED • TABLE_PER_CLASS

22. Inheritance Example 1 @Entity @Inheritance(strategy=InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name="DISC", discriminatorType=DiscriminatorType.STRING) @DiscriminatorValue("CUSTOMER") public class Customer { . . . } @Entity @DiscriminatorValue("VCUSTOMER") public class ValuedCustomer extends Customer { . . . } • SINGLE_TABLE strategy - all classes in the hierarchy are mapped to a single table in the database • Discriminator column - contains a value that identifies the subclass • Discriminator type - {STRING, CHAR, INTEGER} • Discriminator value - value entered into the discriminator column for each entity in a class hierarchy

23. Inheritance Examples 2 & 3 @Entity @Inheritance(strategy=InheritanceType.JOINED) public class Customer { . . . } @Entity public class ValuedCustomer extends Customer { . . . } @Entity @Inheritance(strategy=InheritanceType.TABLE_PER_CLASS) public class Customer { @Id @GeneratedValue(strategy = GenerationType.TABLE) private Long id; . . . } @Entity public class ValuedCustomer extends Customer { . . . }

24. Inheritance Example 3 @Entity @Inheritance(strategy=InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name="DISC", discriminatorType=DiscriminatorType.STRING) @DiscriminatorValue("CUSTOMER") public class Customer { . . . } @Entity @DiscriminatorValue("VCUSTOMER") public class ValuedCustomer extends Customer { . . . } • SINGLE_TABLE strategy - all classes in the hierarchy are mapped to a single table in the database • Discriminator column - contains a value that identifies the subclass • Discriminator type - {STRING, CHAR, INTEGER} • Discriminator value - value entered into the discriminator column for each entity in a class hierarchy

25. Managing Entities • Entities are managed by the entity manager • The entity manager is represented by javax.persistence.EntityManager instances • Each EntityManager instance is associated with a persistence context • A persistence context defines the scope under which particular entity instances are created, persisted, and removed

26. Persistence Context • A persistence context is a set of managed entity instances that exist in a particular data store • Entities are keyed by their persistent identity • Only one entity with a given persistent identity may exist in the persistence context • Entities are added to the persistence context, but are not individually removable (“detached”) • Controlled and managed by EntityManager • Contents of persistence context change as a result of operations on EntityManager API

27. Persistence Context Persistence Context Application EntityManager MyEntity A MyEntity C MyEntity a MyEntity B MyEntity b Entities Entity state

28. Entity Manager • An EntityManager instance is used to manage the state and life cycle of entities within a persistence context • The EntityManager API: • creates and removes persistent entity instances • finds entities by the entity’s primary key • allows queries to be run on entities • There are two types of EntityManagers: • Application-Managed EntityManagers • Container-Managed EntityManagers

29. Application-Managed EntityManager Applications create EntityManager instances by using directly Persistence and EntityManagerFactory: • javax.persistence.Persistence • Root class for obtaining an EntityManager • Locates provider service for a named persistence unit • Invokes on the provider to obtain an EntityManagerFactory • javax.persistence.EntityManagerFactory • Creates EntityManagers for a named persistence unit or configuration

30. Application-Managed EntityManager public class PersistenceProgram { public static void main(String[] args) { EntityManagerFactory emf = Persistence.createEntityManagerFactory(“SomePUnit”); EntityManager em = emf.createEntityManager(); em.getTransaction().begin(); // Perform finds, execute queries, // update entities, etc. em.getTransaction().commit(); em.close(); emf.close(); } }

31. Container-Managed EntityManagers An EntityManager with a transactional persistence context can be injected by using the @PersistenceContext annotation @Transactional public class PersistenceHelperImpl implements PersistenceHelper { . . . @PersistenceContext publicvoid setEntityManager(EntityManager em) { this.em = em; } publicvoid save(PersistentEntity object) { if (object.getId() == null) { getEntityManager().persist(object); } else { getEntityManager().merge(object); } } }

32. Transactions • JPA transactions can be managed by: • the users application • a framework (such as Spring) • a JavaEE container • Transactions can be controller in two ways: • Java Transaction API (JTA) • container-managed entity manager • EntityTransaction API (tx.begin(), tx.commit(), etc) • application-managed entity manager

33. Operations on Entity Objects • EntityManager API operations: • persist()- Insert the state of an entity into the db • remove()- Delete the entity state from the db • refresh()- Reload the entity state from the db • merge()- Synchronize the state of detached entity with the pc • find()- Execute a simple PK query • createQuery()- Create query instance using dynamic JP QL • createNamedQuery()- Create instance for a predefined query • createNativeQuery()- Create instance for an SQL query • contains()- Determine if entity is managed by pc • flush()- Force synchronization of pc to database

34. Entity Instance’s Life Cycle • Instances are in one of four states: • New • Managed • Detached • Removed • The state of persistent entities is synchronized to the database when the transaction commits • To force synchronization of the managed entity to the data store, invoke the flush() method

35. Persistence Units • A persistence unit defines a set of all entity classes that are managed by EntityManager instances in an application • For example, some set of entities can share one common provider (TopLink), whereas other set of entities can depend on a different provider (Hibernate) • Persistence units are defined by the persistence.xml configuration file

36. persistence.xml A persistence.xml file defines one or more persistence units <persistence> <persistence-unit name=" MyMobilePersistentUnit"> <provider>oracle.toplink.essentials.ejb.cmp3.EntityManagerFactoryProvider </provider> <jta-data-source> jdbc/sample </jta-data-source> <class>com.javabeat.ejb30.persistence.entities.mobile.MobileEntity</class> </persistence-unit> <persistence-unit name=" MyOtherPersistentUnit"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <jta-data-source>jdbc/sample</jta-data-source> <class>com.javabeat.ejb30.persistence.entities.mobile.OtherEntity</class> </persistence-unit> </persistence>

37. HibernatePersistence provider • Sample configuration: <persistence-unit name="hibernate_mysql" transaction-type="RESOURCE_LOCAL"> <provider>org.hibernate.ejb.HibernatePersistence</provider> <properties> <property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/> <property name="hibernate.hbm2ddl.auto" value=“update"/> <property name="hibernate.connection.driver_class" value="com.mysql.jdbc.Driver"/> <property name="hibernate.connection.username" value=“newsfeed_user"/> <property name="hibernate.connection.password" value=“newsfeed_pass"/> <property name="hibernate.connection.url" value="jdbc:mysql://localhost/newsfeed"/> <property name="hibernate.show_sql" value="true"> </persistence-unit>

38. hibernate.hbm2ddl.auto • Automatically validates or exports schema DDL to the database when the SessionFactory is created. With create-drop, the database schema will be dropped when the SessionFactory is closed explicitly • Possible values: • validate • create • update • create-drop

39. Example of Spring Configuration EntityManager injection <bean id="entityManagerFactory“ class="org.springframework.orm .jpa.LocalContainerEntityManagerFactoryBean"> <property name="persistenceUnitName" value="hibernate_mysql"/> <property name="jpaVendorAdapter"> <bean class="org.springframework.orm .jpa.vendor.HibernateJpaVendorAdapter“ /> </property> </bean>

40. Example of Spring Configuration Transaction Manager injection <bean id="transactionManager“ class="org.springframework.orm .jpa.JpaTransactionManager"> <property name="entityManagerFactory" ref="entityManagerFactory"/> </bean> <tx:annotation-driven transaction-manager="transactionManager"/>

41. JPA exceptions • All exceptions are unchecked • Exceptions in javax.persistence package are self-explanatory http://openjpa.apache.org/docs/openjpa-0.9.0-incubating/manual/manual.html

42. JPQL Java Persistence Query Language

43. Introduction • The Java Persistence API specifies a query language that allowsto define queries over entities and their persistent state • JPQL is an extension of EJB QL • More robust flexible and object-oriented than SQL • The persistence engine parse the query string, transform the JPQL to the native SQL before executing it

44. Creating Queries • Query instances are obtained using: • EntityManager.createNamedQuery(static query) • EntityManager.createQuery (dynamic query) • Query API: getResultList() – execute query returning multiple results getSingleResult()– execute query returning single result executeUpdate()– execute bulk update or delete setFirstResult()– set the first result to retrieve setMaxResults()– set the maximum number of results to retrieve setParameter()– bind a value to a named or positional parameter setHint()– apply a vendor-specific hint to the query setFlushMode()– apply a flush mode to the query when it gets run

45. Static (Named) Queries • Defined statically with the help of @NamedQueryannotation together with the entity class • @NamedQuery elements: • name - the name of the query that will be used with the createNamedQuery method • query – query string @NamedQuery(name="findAllCustomers", query="SELECT c FROM Customer") Query findAllQuery = entityManager.createNamedQuery(“findAllCustomers”); List customers = findAllQuery.getResultList();

46. Multiple Named Queries Multiple named queries can be logically defined with the help of @NamedQueries annotation @NamedQueries( { @NamedQuery(name = “Mobile.selectAllQuery” query = “SELECT M FROM MOBILEENTITY”), @NamedQuery(name = “Mobile.deleteAllQuery” query = “DELETE M FROM MOBILEENTITY”) } )

47. Dynamic Queries • Dynamic queries are queries that are defined directly within an application’s business logic • Worse efficiency and slower query execution, as the persistence engine has to do all the parsing and validation stuffs, along with mapping the JPQL to the SQL at the run-time public List findAll(String entityName){ return entityManager.createQuery( "select e from " + entityName + " e") .getResultList(); }

48. Named Parameters • Named parameters are parameters in a query that are prefixed with a colon (:) • To bound parameter to an argument use method: • Query.setParameter(String name, Object value) public List findWithName(String name) { return em.createQuery( "SELECT c FROM Customer c WHERE c.name LIKE :custName") .setParameter("custName", name) .getResultList(); }

49. Positional Parameters • Positional parameters are prefixed with a question mark (?) followed the numeric position of the parameter in the query • To set parameter values use method: • Query.setParameter(integer position, Object value) public List findWithName(String name) { return em.createQuery( “SELECT c FROM Customer c WHERE c.name LIKE ?1”) .setParameter(1, name) .getResultList(); }

50. Native Queries • Queries may be expressed in native SQL • Support for cases where it is necessary to use the native SQL of the target database in use Query q = em.createNativeQuery( "SELECT o.id, o.quantity, o.item " + "FROM Order o, Item i " + "WHERE (o.item = i.id) AND (i.name = 'widget')", com.acme.Order.class); • @SqlResultSetMapping annotaton is used for more advanced cases