Difference between revisions of "EclipseLink/UserGuide/JPA/Advanced JPA Development/Composite Persistence Units"

From Eclipsepedia

Jump to: navigation, search
m
(Example)
(31 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{EclipseLink_UserGuide
+
{{EclipseLink_UserGuide  
 
|info=y
 
|info=y
 
|toc=n
 
|toc=n
 +
|eclipselink=y
 +
|eclipselinktype=JPA
 
|api=y
 
|api=y
 
|apis=
 
|apis=
*[http://www.eclipse.org/eclipselink/api/2.3/org/eclipse/persistence/xxx.html xxx]
+
* [[http://www.eclipse.org/eclipselink/api/2.3/org/eclipse/persistence/config/EntityManagerProperties.html EntityManagerProperties]]
 
|examples=y
 
|examples=y
 
|example=
 
|example=
*[[EclipseLink/Examples/JPA/MetadataSource|MetadataSource]]
+
*[[http://wiki.eclipse.org/EclipseLink/Examples/JPA/Composite Composite Persistence Units Example]]
}}  
+
}}
  
= Composite Persitence Units=
+
= Composite Persistence Units=
  
''This feature is new in EclipseLink 2.3.''
+
{{EclipseLink_NewIn
 +
|version=2.3}}
 +
<br>
 +
<br>
  
''This page is under development.''
+
Multiple persistence units with unique sets of entity types can be exposed as a single persistence context by using a ''composite persistence unit''. A persistent unit that is part of a composite persistent unit is called a ''composite member persistent unit''.
  
You can store mapping information outside an application and then the mapping information retrieved when the application's persistence unit is created. This feature can be used for any mapping customization including Extensible JPA Entities.  
+
With composite persistence units:
 +
* Mapping relationships can be established among any of the entities in the composite.
 +
* The persistence context can access entities stored in different data sources.
 +
* Queries and transactions can be performed transparently across the complete set of entities.  
  
{{EclipseLink_JPA
+
For example, you could persist data from a single context into different data sources, as shown below:
|up=     [[EclipseLink/UserGuide/JPA/Advanced_JPA_Development|Advanced JPA Development]]
+
 
}}
+
<source lang="java">
 +
em.persist(new A(..));
 +
em.persist(new Z(..));
 +
// Insert A into database1; insert Z into database2:
 +
// the two databases can be from different vendors.
 +
em.flush();
 +
</source>
 +
 
 +
 
 +
==Configuring Composite Persistence and Composite Member Persistence Units ==
 +
 
 +
Both composite persistence units and their member persistence units are regular persistence units, each of them must have persistence.xml.
 +
 
 +
===Configuring Composite Persistent Units in persistence.xml ===
 +
 
 +
* Use the <tt><property name="eclipselink.composite-unit" value="true"/></tt> property to identify persistence unit as a composite. ('''Note:''' If this property is passed to the <tt>createEntityManagerFactory</tt> method or if it is set in system properties, it is ignored.)
 +
 
 +
* Use the <tt><jar-file></tt> element to specify the jar files containing the composite member persistent units. The composite persistence unit will contain all the persistence units found in the jar files specified.
 +
 
 +
* The transaction type may be specified in the composite persistence unit (otherwise default transaction type is used). Transaction types of composite members are ignored.
 +
* [[#Persistence Unit Properties That Can Be Set on Composite Persistence Units| Persistence Unit Properties That Can Be Set on Composite Persistence Units]] (like "eclipselink.target-server") may be specified in composite pu persistence.xml (these properties ignored if specified by composite members).
 +
* Don't specify any classes in composite persistence unit - all the classes should be specified in composite members.
 +
 
 +
====Example====
 +
The composite persistence unit <tt>compositePu</tt> specifies the transaction type and the server platform. It will contain all persistence units defined in <tt>member1.jar</tt> and <tt>member2.jar</tt> files.
 +
 
 +
<source lang="xml">
 +
<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence persistence_1_0.xsd" version="1.0">
 +
    <persistence-unit name="compositePu" transaction-type="JTA">
 +
        <provider>
 +
            org.eclipse.persistence.jpa.PersistenceProvider
 +
        </provider>
 +
 
 +
        <jar-file>member1.jar</jar-file>
 +
        <jar-file>member2.jar</jar-file>
 +
 
 +
        <properties>
 +
            <property name="eclipselink.composite-unit" value="true"/>
 +
            <property name="eclipselink.target-server" value="WebLogic_10"/>
 +
        </properties>
 +
    </persistence-unit>
 +
</persistence>
 +
</source>
 +
 
 +
===Configuring Composite Member Persistent Units in persistence.xml ===
 +
* Data sources may be specified in composite member persistence units.  Those specified in the composite are ignored.
 +
* [[#Persistence Unit Properties That Can Be Set on Composite Member Persistence Units| Persistence Unit Properties That Can Be Set on Composite Member Persistence Units]] (like "eclipselink.target-database") may be specified in composite members pu persistence.xml (these properties ignored if specified by the composite pu).
 +
* Normally composite member pu could also be used as stand alone pu (independent from the composite). However if a member pu has dependencies of another member(s) (for instance a class defined in memberPu2 has a reference to a class defined in memberPu1) then such pu can no longer be used as a stand alone - only as a member of the composite.
 +
** To indicate that a member pu ''must'' be a member of a composite pu <property name="eclipselink.composite-unit.member" value="true"/> should be specified in its persistence.xml. ('''Note:''' If this property is passed to the <tt>createEntityManagerFactory</tt> method or if it is set in system properties, it is ignored.)
 +
*** Attempt to create an EntityManagerFactory for such pu will still succeed (that's required by application servers), however attempt to create an EntityManager from the factory would fail
 +
 
 +
====Example====
 +
Composite member persistence unit <tt>memberPu1</tt> is defined in the <tt>member1.jar</tt> file. It can be used independently as well as inside composite persistence unit.
 +
Note that transaction type and server platform will be ignored if memberPu1 used as a composite member pu, but they will be used if memberPu1 is used stand alone (as a regular persistence unit).
 +
<source lang="xml">
 +
<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence persistence_1_0.xsd" version="1.0">
 +
    <persistence-unit name="memberPu1" transaction-type="JTA">
 +
        <provider>
 +
            org.eclipse.persistence.jpa.PersistenceProvider
 +
        </provider>
 +
        <mapping-file>META-INF/advanced-entity-mappings1.xml</mapping-file>
 +
        <jta-data-source>jdbc/OracleJtaDS</jta-data-source>
 +
        <exclude-unlisted-classes>false</exclude-unlisted-classes>
 +
        <properties>
 +
            <property name="eclipselink.target-server" value="WebLogic_10"/>
 +
            <property name="eclipselink.target-database" value="org.eclipse.persistence.platform.database.oracle.Oracle11Platform"/>
 +
        </properties>
 +
    </persistence-unit>
 +
</persistence>
 +
</source>
 +
 
 +
Composite member persistence unit <tt>memberPu2</tt> is defined in the <tt>member2.jar</tt> file. It has dependency on a class defined in member1.jar and cannot be used independently.
 +
 
 +
<source lang="xml">
 +
<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence persistence_1_0.xsd" version="1.0">
 +
    <persistence-unit name="memberPu2">
 +
        <provider>
 +
            org.eclipse.persistence.jpa.PersistenceProvider
 +
        </provider>
 +
        <mapping-file>META-INF/advanced-entity-mappings2.xml</mapping-file>
 +
        <jta-data-source>jdbc/MySqlJtaDS</jta-data-source>
 +
        <exclude-unlisted-classes>false</exclude-unlisted-classes>
 +
        <properties>
 +
            <property name="eclipselink.composite-unit.member" value="true"/>
 +
            <property name="eclipselink.target-database" value="org.eclipse.persistence.platform.database.MySQLPlatform"/>
 +
        </properties>
 +
    </persistence-unit>
 +
</persistence>
 +
</source>
 +
 
 +
<!---//REVIEWERS: Design doc also says "If this property is set to true, the EntityManagerFactory can still be created, but it cannot be connected." I don't understand, as true is perfectly valid, no?// //ANDREI: true is perfectly valid. That means persistence unit can only be used as a member of composite - cannot be used as an independent persistence unit. Motivation: persistence unit that has dependency on classes in other persistence unit(s) - impossible to use standalone, still possible to use as a member of composite, of course the persistence unit(s) on which it depends should also be members in the same composite. Logically I would prefer to fail when the factory is created - but that would be a problem with application servers, so the next best solution is to fail on attempt to actually use the factory - createEntityManager// -->
 +
 
 +
== Persistence Unit Properties ==
 +
As always, Persistence Unit properties could be either defined in persistence.xml or passed to createEntityManagerFactory method (the latter properties overriding the former).
 +
 
 +
===Example===
 +
Property "eclipselink.logging.level" passed to the composite persistence unit, connection properties passed to the member persistence units through "eclipselink.composite-unit.properties" property.
 +
<source lang="java">
 +
Map props1 = new HashMap();
 +
 
 +
  props1.put("javax.persistence.jdbc.user", "user1");
 +
  props1.put("javax.persistence.jdbc.password", "password1");
 +
  props1.put("javax.persistence.jdbc.driver", "oracle.jdbc.OracleDriver");
 +
  props1.put("javax.persistence.jdbc.url", "jdbc:oracle:thin:@oracle_db_url:1521:db");
 +
 
 +
Map props2 = new HashMap();
 +
 
 +
  props2.put("javax.persistence.jdbc.user", "user2");
 +
  props2.put("javax.persistence.jdbc.password", "password2");
 +
  props2.put("javax.persistence.jdbc.driver", "com.mysql.jdbc.Driver");
 +
  props2.put("javax.persistence.jdbc.url", " jdbc:mysql://my_sql_db_url:3306/user2");
 +
 
 +
Map memberProps = new HashMap();
 +
  memberProps.put("memberPu1", props1);
 +
  memberProps.put("memberPu2", props2);
 +
 
 +
Map props = new HashMap();
 +
  props.put("eclipselink.logging.level", "FINEST");
 +
  props.put("eclipselink.composite-unit.properties", memberProps);
 +
 
 +
EntityManagerFactory emf = Persistence.createEntityManagerFactory("compositePu", props);
 +
 
 +
</source>
 +
 
 +
The following tables show where to set properties: on the composite persistence unit or on the composite member persistence unit.
 +
 
 +
* [[#Persistence Unit Properties That Can Be Set on Composite Persistence Units| Persistence Unit Properties That Can Be Set on Composite Persistence Units]] should be used only by the composite persistence unit.
 +
* [[#Persistence Unit Properties That Can Be Set on Composite Member Persistence Units| Persistence Unit Properties That Can Be Set on Composite Member Persistence Units]] should be used only by composite member persistence units.
 +
* Composite pu member property used assigned to composite pu (or composite property assigned to composite member pu) is ignored.
 +
 
 +
For complete <tt>PersistenceUnitProperties</tt> reference documentation, see [[http://www.eclipse.org/eclipselink/api/latest/org/eclipse/persistence/config/PersistenceUnitProperties.html |PersistenceUnitProperties]].
 +
 
 +
===Persistence Unit Properties That Can Be Set on Composite Persistence Units===
 +
 
 +
You can set the following persistence unit properties on composite persistence units. All other properties will be ignored.
 +
 
 +
{|{{BMTableStyle}}
 +
|-{{BMTableCaptionStyle
 +
|caption=Persistence Unit Properties Set on Composite Persistence Units}}
 +
|-{{BMTHStyle}}
 +
| PersistenceUnitProperties.
 +
| Property Name
 +
| comment
 +
|-
 +
| COMPOSITE_UNIT
 +
| eclipselink.composite-unit
 +
| Must be specified in persistence.xml of a composite persistence unit with the value "true". Advanced usage: This property can also be set on a composite member persistence unit that is itself a composite persistence unit. In that case, the composite is substituted by its own members.
 +
|-
 +
| COMPOSITE_PROPERTIES
 +
| eclipselink.composite.properties
 +
|
 +
|-
 +
| TRANSACTION_TYPE
 +
| javax.persistence.transactionType
 +
|
 +
|-
 +
| TARGET_SERVER
 +
| eclipselink.target-server
 +
|
 +
|-
 +
| LOGGING_*
 +
| eclipselink.logging.*
 +
|
 +
|-
 +
| PROFILER
 +
| eclipselink.profiler
 +
|
 +
|-
 +
| COORDINATION_*
 +
| eclipselink.cache.coordination.*
 +
|
 +
|-
 +
| SESSION_NAME
 +
| eclipselink.session-name
 +
| This property can also be set on a composite member persistence unit . The member session name is used to read the session from <tt>sessions.xml</tt>, but the deployed session always has the same name as the member persistence unit (as it is defined in <tt>memberPuInfo.getPersistenceUnitName()</tt>)
 +
|-
 +
| DEPLOY_ON_STARTUP
 +
| eclipselink.deploy-on-startup
 +
|
 +
|-
 +
| VALIDATION_ONLY_PROPERTY
 +
| eclipselink.validation-only
 +
| In 2.3: This property is also processed if set on a composite member persistence unit, but that is a known bug ({{bug|348815}}). This property '''should''' be processed by the composite only and ignored by member persistence units. To work around this bug, specify the property in the composite and in all its members. THIS IS FIXED IN 2.3.1: it's ignored by members.
 +
|-
 +
| VALIDATION_*
 +
| eclipselink.validation.*
 +
|
 +
|-
 +
| CLASSLOADER
 +
| eclipselink.classloader
 +
|
 +
|-
 +
| THROW_EXCEPTIONS
 +
| eclipselink.orm.throw.exceptions
 +
|
 +
|-
 +
| FLUSH_CLEAR_CACHE
 +
| eclipselink.flush-clear.cache
 +
|
 +
|-
 +
| VALIDATE_EXISTENCE
 +
| eclipselink.validate-existence
 +
|
 +
|-
 +
| JOIN_EXISTING_TRANSACTION
 +
| eclipselink.transaction.join-existing
 +
|
 +
|-
 +
| PERSISTENCE_CONTEXT_*
 +
| eclipselink.persistence-context.*
 +
|
 +
|-
 +
| ALLOW_ZERO_ID
 +
| eclipselink.allow-zero-id
 +
|
 +
|-
 +
| SESSION_CUSTOMIZER
 +
| eclipselink.session.customizer
 +
| This property can also be set on a composite member persistence unit. Customizers of member persistence units are processed before the composite persistence unit's customizer.
 +
|-
 +
| SESSION_EVENT_LISTENER_CLASS
 +
| eclipselink.session-event-listener
 +
|This property can also be set on a composite member persistence unit. An
 +
<tt>EventListener</tt> defined by a composite member will not receive events raised by a <tt>UnitOfWork</tt>; it will only receive events raised by its member. Also see {{bug|348766}} - FIXED in 2.3.1. An <tt>EventListener<>/tt> specified by a composite will receive all events (raised by either a unit of work or by members).
 +
|-
 +
| Exception_HANDLER_CLASS
 +
| eclipselink.exception-handler
 +
| This property can also be set on a composite member persistence unit. The first <tt>ExceptionHandler</tt> specified by a member handles the exception. If it is not specified or fails, then the composite's <tt>ExceptionHandler</tt> handles the original exception.
 +
|-
 +
| WEAVING
 +
| eclipselink.weaving
 +
| A composite persistent unit switches weaving on and off for all its member persistent units.
 +
|-
 +
|}
 +
 
 +
===Persistence Unit Properties That Can Be Set on Composite Member Persistence Units===
 +
 
 +
You can set the following persistence unit properties on composite member persistence units. All other properties will be ignored.
 +
 
 +
{|{{BMTableStyle}}
 +
|-{{BMTableCaptionStyle
 +
|caption=Persistence Unit Properties Set on Composite Member Persistence Units}}
 +
|-{{BMTHStyle}}
 +
| PersistenceUnitProperties.
 +
| Property Name
 +
| comment
 +
|-
 +
| COMPOSITE_UNIT
 +
| eclipselink.composite-unit
 +
| Advanced usage: This property can also be set on a composite member persistence unit that is itself a composite persistence unit. In that case, the composite is substituted by its own members. 
 +
|-
 +
| COMPOSITE_UNIT_MEMBER
 +
| eclipselink.composite-unit.member
 +
|The property should be specified with a value "true" in persistence.xml to indicate that the persistence unit cannot be used stand alone (only as a member of a composite).
 +
|-
 +
| SESSION_NAME
 +
| eclipselink.session-name
 +
| This property can also be set on a composite persistence unit. The member session name is used to read the session from <tt>sessions.xml</tt>, but the deployed session always has the same name as the member persistence unit (as it is defined in <tt>memberPuInfo.getPersistenceUnitName()</tt>)
 +
|-
 +
| VALIDATION_ONLY_PROPERTY
 +
| eclipselink.validation-only
 +
| This property is processed if set on a composite member persistence unit, but that is a known bug ({{bug|348815}}). This property '''should''' be processed by the composite only and ignored by member persistence units. To work around this bug, specify the property in the composite and in all its members. FIXED in 2.3.1 - ignored on member.
 +
|-
 +
| VALIDATION_*
 +
| eclipselink.validation.*
 +
|
 +
|-
 +
| CLASSLOADER
 +
| eclipselink.classloader
 +
|
 +
|-
 +
| THROW_EXCEPTIONS
 +
| eclipselink.orm.throw.exceptions
 +
|
 +
|-
 +
| FLUSH_CLEAR_CACHE
 +
| eclipselink.flush-clear.cache
 +
|
 +
|-
 +
| VALIDATE_EXISTENCE
 +
| eclipselink.validate-existence
 +
|
 +
|-
 +
| JOIN_EXISTING_TRANSACTION
 +
| eclipselink.transaction.join-existing
 +
|
 +
|-
 +
| PERSISTENCE_CONTEXT_*
 +
| eclipselink.persistence-context.*
 +
|
 +
|-
 +
| ALLOW_ZERO_ID
 +
| eclipselink.allow-zero-id
 +
|
 +
|-
 +
| SESSION_CUSTOMIZER
 +
| eclipselink.session.customizer
 +
| This property can also be set on a composite persistence unit. Customizers of member persistence units are processed before the composite persistence unit's customizer.
 +
|-
 +
| SESSIONS_XML
 +
| eclipselink.sessions-xml
 +
|If this property is set on a composite persistence unit, an exception will be thrown. Composite persitence units cannot be read from <tt>sessions.xml</tt>. Note that a non-composite persistence unit should be able to use a <tt>SessionBroker</tt> defined in <tt>sessions.xml</tt>.
 +
|-
 +
| JTA_DATASOURCE
 +
| javax.persistence.jtaDataSource
 +
|
 +
|-
 +
| NON_JTA_DATASOURCE
 +
| javax.persistence.nonJtaDataSource
 +
|
 +
|-
 +
| NATIVE_SQL
 +
| eclipselink.jdbc.native-sql
 +
|
 +
|-
 +
| SQL_CAST
 +
| eclipselink.jdbc.sql-cast
 +
|
 +
|-
 +
| JDBC_*
 +
| javax.persistence.jdbc.* eclipselink.jdbc.*
 +
|
 +
|-
 +
| CONNECTION_POOL_*
 +
|
 +
|
 +
|-
 +
| PARTITIONING.*
 +
| eclipselink.partitioning.*
 +
|
 +
|-
 +
| EXCLUSIVE_CONNECTION_*
 +
| eclipselink.jdbc.exclusive-connection.*
 +
|
 +
|-
 +
| CACHE.*
 +
| eclipselink.cache.*
 +
|
 +
|-
 +
| TARGET_DATABASE
 +
| eclipselink.target-database
 +
|
 +
|-
 +
| TABLE_CREATION_SUFFIX
 +
| eclipselink.ddl-generation.table-creation-suffix
 +
|
 +
|-
 +
| EXCLUDE_ECLIPSELINK_ORM_FILE
 +
| eclipselink.exclude-eclipselink-orm
 +
|
 +
|-
 +
| WEAVING_*
 +
| eclipselink.weaving.*
 +
| If the weaving is on, members use their own weaving properties.
 +
|-
 +
| NATIVE_QUERY_UPPERCASE_COLUMNS
 +
| eclipselink.jdbc.uppercase-columns
 +
|
 +
|-
 +
| UPPERCASE_COLUMN_NAMES
 +
| eclipselink.jpa.uppercase-column-names
 +
|
 +
|-
 +
| BATCH_WRITING.*
 +
| eclipselink.jdbc.batch-writing.*
 +
|
 +
|-
 +
| SESSION_EVENT_LISTENER_CLASS
 +
| eclipselink.session-event-listener
 +
|This property can also be set on a composite persistence unit. An <tt>EventListener</tt> defined by a composite member will not receive events raised by a <tt>UnitOfWork</tt>; it will only receive events raised by its member. Also see {{bug|348766}}. An <tt>EventListener<>/tt> specified by a composite will receive all events (raised by either a unit of work or by members).
 +
|-
 +
| Exception_HANDLER_CLASS
 +
| eclipselink.exception-handler
 +
| This property can also be set on a composite persistence unit. The first <tt>ExceptionHandler</tt> specified by a member handles the exception. If it is not specified or fails, then the composite's <tt>ExceptionHandler</tt> handles the original exception.
 +
|-
 +
| INCLUDE_DESCRIPTOR_QUERIES
 +
| eclipselink.session.include.descriptor.queries
 +
|
 +
|-
 +
| ID_VALIDATION
 +
| eclipselink.id-validation
 +
|
 +
|-
 +
| TEMPORAL_MUTABLE
 +
| eclipselink.temporal.mutable
 +
|
 +
|-
 +
| ORM_SCHEMA_VALIDATION
 +
| eclipselink.orm.validate.schema
 +
|
 +
|-
 +
| DDL_*
 +
|
 +
|
 +
|-
 +
| PESSIMISTIC_LOCK_TIMEOUT
 +
| javax.persistence.lock.timeout
 +
|
 +
|-
 +
| QUERY_TIMEOUT
 +
| javax.persistence.query.timeout
 +
|
 +
|-
 +
| ORACLE_PROXY_TYPE
 +
| eclipselink.oracle.proxy-type
 +
|
 +
|}
 +
 
 +
<br>
 +
 
 +
== Entity Manager Properties ==
 +
 
 +
As always, Entity Manager properties can be set either through either <tt>createEntityManager()</tt> method on the factory or to the <tt>setProperty</tt> method on the EntityManager.
 +
 
 +
===Example===
 +
Property ""eclipselink.jdbc.exclusive-connection.mode"" passed to the composite persistence unit, connection properties passed to the member persistence units through "eclipselink.composite-unit.properties" property.
 +
<source lang="java">
 +
Map props1 = new HashMap();
 +
 
 +
  props1.put("javax.persistence.jdbc.user", "user1");
 +
  props1.put("javax.persistence.jdbc.password", "password1");
 +
  props1.put("javax.persistence.jdbc.driver", "oracle.jdbc.OracleDriver");
 +
  props1.put("javax.persistence.jdbc.url", "jdbc:oracle:thin:@oracle_db_url:1521:db");
 +
 
 +
Map props2 = new HashMap();
 +
 
 +
  props2.put("javax.persistence.jdbc.user", "user2");
 +
  props2.put("javax.persistence.jdbc.password", "password2");
 +
  props2.put("javax.persistence.jdbc.driver", "com.mysql.jdbc.Driver");
 +
  props2.put("javax.persistence.jdbc.url", " jdbc:mysql://my_sql_db_url:3306/user2");
 +
 
 +
Map memberProps = new HashMap();
 +
  memberProps.put("memberPu1", props1);
 +
  memberProps.put("memberPu2", props2);
 +
 
 +
Map props = new HashMap();
 +
  props.put("eclipselink.jdbc.exclusive-connection.mode", "Always");
 +
  props.put("eclipselink.composite-unit.properties", memberProps);
 +
 
 +
EntityManager em = emf.createEntityManager(props);
 +
 
 +
</source>
 +
 
 +
The following tables show where to set properties: on the composite persistence unit or on the composite member persistence unit.
 +
 
 +
* [[#Entity Manager Properties That Can Be Set On Composite Persistence Units| Entity Manager Properties That Can Be Set On Composite Persistence Units]] should be used only by the composite persistence unit.
 +
* [[#Entity Manager Properties That Can Be Set On Composite Member Persistence Units| Entity Manager Properties That Can Be Set On Composite Member Persistence Units]] should be used only by composite member persistence units.
 +
* Composite pu member property used assigned to composite pu (or composite property assigned to composite member pu) is ignored.
 +
 
 +
For complete <tt>PersistenceUnitProperties</tt> reference documentation, see [[http://www.eclipse.org/eclipselink/api/latest/org/eclipse/persistence/config/EntityManagerProperties.html |EntityManagerProperties]].
 +
 
 +
===Entity Manager Properties That Can Be Set On Composite Persistence Units===
 +
 
 +
You can set the following entity manager properties on composite persistence units. All other properties will be ignored.
 +
 
 +
{|{{BMTableStyle}}
 +
|-{{BMTHStyle}}
 +
| EntityManagerProperties.
 +
| Property Name
 +
|-
 +
| COMPOSITE_PROPERTIES
 +
| eclipselink.composite.properties
 +
|-
 +
| FLUSH_CLEAR_CACHE
 +
| eclipselink.flush-clear.cache
 +
|-
 +
| VALIDATE_EXISTENCE
 +
| eclipselink.validate-existence
 +
|-
 +
| JOIN_EXISTING_TRANSACTION
 +
| eclipselink.transaction.join-existing
 +
|-
 +
| PERSISTENCE_CONTEXT_*
 +
| eclipselink.persistence-context.*
 +
|-
 +
| ORDER_UPDATES
 +
| eclipselink.order-updates
 +
|-
 +
|}
 +
 
 +
===Entity Manager Properties That Can Be Set On Composite Member Persistence Units===
 +
 
 +
You can set the following entity manager properties on composite member persistence units. All other properties will be ignored.
 +
 
 +
{|{{BMTableStyle}}
 +
|-{{BMTHStyle}}
 +
| EntityManagerProperties.
 +
| Property Name
 +
|-
 +
| EXCLUSIVE_CONNECTION_*
 +
| eclipselink.jdbc.exclusive-connection.*
 +
|-
 +
| JDBC_DRIVER
 +
| javax.persistence.jdbc.driver
 +
|-
 +
| JDBC_URL
 +
| javax.persistence.jdbc.url
 +
|-
 +
| JDBC_USER
 +
| javax.persistence.jdbc.user
 +
|-
 +
| JDBC_PASSWORD
 +
| javax.persistence.jdbc.password
 +
|-
 +
| JTA_DATASOURCE
 +
| javax.persistence.jtaDataSource
 +
|-
 +
| NON_JTA_DATASOURCE
 +
| javax.persistence.nonJtaDataSource
 +
|-
 +
| CONNECTION_POLICY
 +
| eclipselink.jdbc.connection-policy
 +
|-
 +
| ORACLE_PROXY_TYPE
 +
| eclipselink.oracle.proxy-type
 +
|}
 +
 
 +
==Deploying and Accessing a Composite Persistence Unit==
 +
 
 +
All the jars – the composite and the members – should be deployed on the same class loader. If they are deployed to an application server, the jars should be packed in an ear file. If they run standalone, the jars should be added to the class path.
 +
 
 +
A composite persistence unit can be accessed as any other persistence unit.
 +
 
 +
* Container managed composite persistence unit could be accessed using injection:
 +
 
 +
<source lang="java">
 +
@PersistenceUnit(unitName="compositePu")
 +
EntityManagerFactory entityManagerFactory;
 +
@PersistenceUnit(unitName="compositePu")
 +
EntityManager entityManager;
 +
</source>
 +
 
 +
* Application managed composite persistence unit - using  [[http://www.eclipse.org/eclipselink/api/latest/javax/persistence/Persistence.html <tt>Persistence.createEntityManagerFactory </tt>]]:
 +
 
 +
<source lang="java">
 +
EntityManagerFactory entityManagerFactory = Persistence.createEntityManagerFactory("compositePu", properties);
 +
</source>
 +
 
 +
== Limitations ==
 +
Composite members persistence units' names must be unique in the composite.
 +
 
 +
Joins across tables in different data sources are not supported. This limitation affects mapping, query execution, and optimizations. For example:
 +
*Entities mapped in different composite members cannot be joined in a query.
 +
* If deleting an entity causes deletion from a table that is mapped by another composite member, then a "delete all" query cannot be performed. Therefore a delete all cannot be used if an entity:
 +
** has <tt>ElementCollection</tt> mapped in another composite member,
 +
** owns bidirectional relationship with a <tt>JoinTable</tt> with the target mapped in another composite member,
 +
** has any reference mapping that is privately owned with the target mapped in another composite member.
 +
 
 +
The inheritance hierarchy cannot be shared between different composite members.
 +
 
 +
If the target of a reference mapping is defined in a different composite member and <tt>JoinTable</tt> is used, the join table must belong to the target composite member. Such mappings must be unidirectional: the "invert" mapping cannot use <tt>mappedBy</tt>. That is because <tt>JoinTable</tt> must be defined in the same composite member with the target entity. Master mapping requires it to be in slave's member, slave mapping - in master's.You can work around this limitation by defining independent invert mapping with its own <tt>JoinTable</tt>. If you maintain both sides of the relationship, the two join tables will be in sync.
 +
 
 +
A native query created without a result class must specify the target composite member persistence unit, for example:
 +
 
 +
<source lang=java>
 +
em.createNativeQuery("SELECT F_NAME FROM MBR2_EMPLOYEE").setHint(QueryHints.COMPOSITE_UNIT_MEMBER, "composite-advanced-member_2").getResultList();
 +
</source>
 +
 
 +
== Extensions ==
 +
You can specify <tt>ElementCollection</tt> with primitive type target values with <tt>CollectionTable</tt> defined in a different composite member persistence unit, using annotations or <tt>eclipselink-orm.xml</tt> as described below:
 +
 
 +
* Annotations
 +
 
 +
<source lang=java>
 +
@ElementCollection()
 +
@CollectionTable(name = "MBR1_RESPONS", joinColumns=@JoinColumn(name="EMP_ID"))
 +
@CompositeMember("composite-advanced-member_1")
 +
@Column(name = "DESCRIPTION")
 +
public Collection<String> getResponsibilities() {
 +
    return responsibilities;
 +
}
 +
</source>
 +
 
 +
* eclipselink-orm.xml
 +
 
 +
<source lang=xml>
 +
<element-collection name="responsibilities" composite-member="xml-composite-advanced-member_3">
 +
    <column name="DESCRIPTION"/>
 +
    <collection-table name="XML_MBR3_RESPONS">
 +
        <join-column name="EMP_ID"/>
 +
    </collection-table>
 +
</element-collection>
 +
</source>
 +
 
 +
No <tt>@CompositeMember</tt> annotation (or <tt>composite-member</tt> attribute) is required if <tt>CollectionTable</tt> is defined in the same composite member persistence unit as the source.

Revision as of 10:18, 20 July 2011

EclipseLink JPA


Composite Persistence Units

EL NewIn.png New in version 2.3.



Multiple persistence units with unique sets of entity types can be exposed as a single persistence context by using a composite persistence unit. A persistent unit that is part of a composite persistent unit is called a composite member persistent unit.

With composite persistence units:

  • Mapping relationships can be established among any of the entities in the composite.
  • The persistence context can access entities stored in different data sources.
  • Queries and transactions can be performed transparently across the complete set of entities.

For example, you could persist data from a single context into different data sources, as shown below:

em.persist(new A(..));
em.persist(new Z(..));
// Insert A into database1; insert Z into database2:
// the two databases can be from different vendors.
em.flush();


Configuring Composite Persistence and Composite Member Persistence Units

Both composite persistence units and their member persistence units are regular persistence units, each of them must have persistence.xml.

Configuring Composite Persistent Units in persistence.xml

  • Use the <property name="eclipselink.composite-unit" value="true"/> property to identify persistence unit as a composite. (Note: If this property is passed to the createEntityManagerFactory method or if it is set in system properties, it is ignored.)
  • Use the <jar-file> element to specify the jar files containing the composite member persistent units. The composite persistence unit will contain all the persistence units found in the jar files specified.
  • The transaction type may be specified in the composite persistence unit (otherwise default transaction type is used). Transaction types of composite members are ignored.
  • Persistence Unit Properties That Can Be Set on Composite Persistence Units (like "eclipselink.target-server") may be specified in composite pu persistence.xml (these properties ignored if specified by composite members).
  • Don't specify any classes in composite persistence unit - all the classes should be specified in composite members.

Example

The composite persistence unit compositePu specifies the transaction type and the server platform. It will contain all persistence units defined in member1.jar and member2.jar files.

<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence persistence_1_0.xsd" version="1.0">
    <persistence-unit name="compositePu" transaction-type="JTA">
        <provider>
            org.eclipse.persistence.jpa.PersistenceProvider
        </provider>
 
        <jar-file>member1.jar</jar-file>
        <jar-file>member2.jar</jar-file>
 
        <properties>
            <property name="eclipselink.composite-unit" value="true"/>
            <property name="eclipselink.target-server" value="WebLogic_10"/>
        </properties>
    </persistence-unit>
</persistence>

Configuring Composite Member Persistent Units in persistence.xml

  • Data sources may be specified in composite member persistence units. Those specified in the composite are ignored.
  • Persistence Unit Properties That Can Be Set on Composite Member Persistence Units (like "eclipselink.target-database") may be specified in composite members pu persistence.xml (these properties ignored if specified by the composite pu).
  • Normally composite member pu could also be used as stand alone pu (independent from the composite). However if a member pu has dependencies of another member(s) (for instance a class defined in memberPu2 has a reference to a class defined in memberPu1) then such pu can no longer be used as a stand alone - only as a member of the composite.
    • To indicate that a member pu must be a member of a composite pu <property name="eclipselink.composite-unit.member" value="true"/> should be specified in its persistence.xml. (Note: If this property is passed to the createEntityManagerFactory method or if it is set in system properties, it is ignored.)
      • Attempt to create an EntityManagerFactory for such pu will still succeed (that's required by application servers), however attempt to create an EntityManager from the factory would fail

Example

Composite member persistence unit memberPu1 is defined in the member1.jar file. It can be used independently as well as inside composite persistence unit. Note that transaction type and server platform will be ignored if memberPu1 used as a composite member pu, but they will be used if memberPu1 is used stand alone (as a regular persistence unit).

<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence persistence_1_0.xsd" version="1.0">
    <persistence-unit name="memberPu1" transaction-type="JTA">
        <provider>
            org.eclipse.persistence.jpa.PersistenceProvider
        </provider>
        <mapping-file>META-INF/advanced-entity-mappings1.xml</mapping-file>
        <jta-data-source>jdbc/OracleJtaDS</jta-data-source>
        <exclude-unlisted-classes>false</exclude-unlisted-classes>
        <properties>
            <property name="eclipselink.target-server" value="WebLogic_10"/>
            <property name="eclipselink.target-database" value="org.eclipse.persistence.platform.database.oracle.Oracle11Platform"/>
        </properties>
    </persistence-unit>
</persistence>

Composite member persistence unit memberPu2 is defined in the member2.jar file. It has dependency on a class defined in member1.jar and cannot be used independently.

<persistence xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence persistence_1_0.xsd" version="1.0">
    <persistence-unit name="memberPu2">
        <provider>
            org.eclipse.persistence.jpa.PersistenceProvider
        </provider>
        <mapping-file>META-INF/advanced-entity-mappings2.xml</mapping-file>
        <jta-data-source>jdbc/MySqlJtaDS</jta-data-source>
        <exclude-unlisted-classes>false</exclude-unlisted-classes>
        <properties>
            <property name="eclipselink.composite-unit.member" value="true"/>
            <property name="eclipselink.target-database" value="org.eclipse.persistence.platform.database.MySQLPlatform"/>
        </properties>
    </persistence-unit>
</persistence>


Persistence Unit Properties

As always, Persistence Unit properties could be either defined in persistence.xml or passed to createEntityManagerFactory method (the latter properties overriding the former).

Example

Property "eclipselink.logging.level" passed to the composite persistence unit, connection properties passed to the member persistence units through "eclipselink.composite-unit.properties" property.

Map props1 = new HashMap();
 
   props1.put("javax.persistence.jdbc.user", "user1");
   props1.put("javax.persistence.jdbc.password", "password1");
   props1.put("javax.persistence.jdbc.driver", "oracle.jdbc.OracleDriver");
   props1.put("javax.persistence.jdbc.url", "jdbc:oracle:thin:@oracle_db_url:1521:db");
 
Map props2 = new HashMap();
 
   props2.put("javax.persistence.jdbc.user", "user2");
   props2.put("javax.persistence.jdbc.password", "password2");
   props2.put("javax.persistence.jdbc.driver", "com.mysql.jdbc.Driver");
   props2.put("javax.persistence.jdbc.url", " jdbc:mysql://my_sql_db_url:3306/user2");
 
Map memberProps = new HashMap();
   memberProps.put("memberPu1", props1);
   memberProps.put("memberPu2", props2);
 
Map props = new HashMap();
   props.put("eclipselink.logging.level", "FINEST");
   props.put("eclipselink.composite-unit.properties", memberProps);
 
EntityManagerFactory emf = Persistence.createEntityManagerFactory("compositePu", props);

The following tables show where to set properties: on the composite persistence unit or on the composite member persistence unit.

For complete PersistenceUnitProperties reference documentation, see [|PersistenceUnitProperties].

Persistence Unit Properties That Can Be Set on Composite Persistence Units

You can set the following persistence unit properties on composite persistence units. All other properties will be ignored.

PersistenceUnitProperties. Property Name comment
COMPOSITE_UNIT eclipselink.composite-unit Must be specified in persistence.xml of a composite persistence unit with the value "true". Advanced usage: This property can also be set on a composite member persistence unit that is itself a composite persistence unit. In that case, the composite is substituted by its own members.
COMPOSITE_PROPERTIES eclipselink.composite.properties
TRANSACTION_TYPE javax.persistence.transactionType
TARGET_SERVER eclipselink.target-server
LOGGING_* eclipselink.logging.*
PROFILER eclipselink.profiler
COORDINATION_* eclipselink.cache.coordination.*
SESSION_NAME eclipselink.session-name This property can also be set on a composite member persistence unit . The member session name is used to read the session from sessions.xml, but the deployed session always has the same name as the member persistence unit (as it is defined in memberPuInfo.getPersistenceUnitName())
DEPLOY_ON_STARTUP eclipselink.deploy-on-startup
VALIDATION_ONLY_PROPERTY eclipselink.validation-only In 2.3: This property is also processed if set on a composite member persistence unit, but that is a known bug (bug 348815). This property should be processed by the composite only and ignored by member persistence units. To work around this bug, specify the property in the composite and in all its members. THIS IS FIXED IN 2.3.1: it's ignored by members.
VALIDATION_* eclipselink.validation.*
CLASSLOADER eclipselink.classloader
THROW_EXCEPTIONS eclipselink.orm.throw.exceptions
FLUSH_CLEAR_CACHE eclipselink.flush-clear.cache
VALIDATE_EXISTENCE eclipselink.validate-existence
JOIN_EXISTING_TRANSACTION eclipselink.transaction.join-existing
PERSISTENCE_CONTEXT_* eclipselink.persistence-context.*
ALLOW_ZERO_ID eclipselink.allow-zero-id
SESSION_CUSTOMIZER eclipselink.session.customizer This property can also be set on a composite member persistence unit. Customizers of member persistence units are processed before the composite persistence unit's customizer.
SESSION_EVENT_LISTENER_CLASS eclipselink.session-event-listener This property can also be set on a composite member persistence unit. An

EventListener defined by a composite member will not receive events raised by a UnitOfWork; it will only receive events raised by its member. Also see bug 348766 - FIXED in 2.3.1. An EventListener<>/tt> specified by a composite will receive all events (raised by either a unit of work or by members).

Exception_HANDLER_CLASS eclipselink.exception-handler This property can also be set on a composite member persistence unit. The first <tt>ExceptionHandler specified by a member handles the exception. If it is not specified or fails, then the composite's ExceptionHandler handles the original exception.
WEAVING eclipselink.weaving A composite persistent unit switches weaving on and off for all its member persistent units.

Persistence Unit Properties That Can Be Set on Composite Member Persistence Units

You can set the following persistence unit properties on composite member persistence units. All other properties will be ignored.

PersistenceUnitProperties. Property Name comment
COMPOSITE_UNIT eclipselink.composite-unit Advanced usage: This property can also be set on a composite member persistence unit that is itself a composite persistence unit. In that case, the composite is substituted by its own members.
COMPOSITE_UNIT_MEMBER eclipselink.composite-unit.member The property should be specified with a value "true" in persistence.xml to indicate that the persistence unit cannot be used stand alone (only as a member of a composite).
SESSION_NAME eclipselink.session-name This property can also be set on a composite persistence unit. The member session name is used to read the session from sessions.xml, but the deployed session always has the same name as the member persistence unit (as it is defined in memberPuInfo.getPersistenceUnitName())
VALIDATION_ONLY_PROPERTY eclipselink.validation-only This property is processed if set on a composite member persistence unit, but that is a known bug (bug 348815). This property should be processed by the composite only and ignored by member persistence units. To work around this bug, specify the property in the composite and in all its members. FIXED in 2.3.1 - ignored on member.
VALIDATION_* eclipselink.validation.*
CLASSLOADER eclipselink.classloader
THROW_EXCEPTIONS eclipselink.orm.throw.exceptions
FLUSH_CLEAR_CACHE eclipselink.flush-clear.cache
VALIDATE_EXISTENCE eclipselink.validate-existence
JOIN_EXISTING_TRANSACTION eclipselink.transaction.join-existing
PERSISTENCE_CONTEXT_* eclipselink.persistence-context.*
ALLOW_ZERO_ID eclipselink.allow-zero-id
SESSION_CUSTOMIZER eclipselink.session.customizer This property can also be set on a composite persistence unit. Customizers of member persistence units are processed before the composite persistence unit's customizer.
SESSIONS_XML eclipselink.sessions-xml If this property is set on a composite persistence unit, an exception will be thrown. Composite persitence units cannot be read from sessions.xml. Note that a non-composite persistence unit should be able to use a SessionBroker defined in sessions.xml.
JTA_DATASOURCE javax.persistence.jtaDataSource
NON_JTA_DATASOURCE javax.persistence.nonJtaDataSource
NATIVE_SQL eclipselink.jdbc.native-sql
SQL_CAST eclipselink.jdbc.sql-cast
JDBC_* javax.persistence.jdbc.* eclipselink.jdbc.*
CONNECTION_POOL_*
PARTITIONING.* eclipselink.partitioning.*
EXCLUSIVE_CONNECTION_* eclipselink.jdbc.exclusive-connection.*
CACHE.* eclipselink.cache.*
TARGET_DATABASE eclipselink.target-database
TABLE_CREATION_SUFFIX eclipselink.ddl-generation.table-creation-suffix
EXCLUDE_ECLIPSELINK_ORM_FILE eclipselink.exclude-eclipselink-orm
WEAVING_* eclipselink.weaving.* If the weaving is on, members use their own weaving properties.
NATIVE_QUERY_UPPERCASE_COLUMNS eclipselink.jdbc.uppercase-columns
UPPERCASE_COLUMN_NAMES eclipselink.jpa.uppercase-column-names
BATCH_WRITING.* eclipselink.jdbc.batch-writing.*
SESSION_EVENT_LISTENER_CLASS eclipselink.session-event-listener This property can also be set on a composite persistence unit. An EventListener defined by a composite member will not receive events raised by a UnitOfWork; it will only receive events raised by its member. Also see bug 348766. An EventListener<>/tt> specified by a composite will receive all events (raised by either a unit of work or by members).
Exception_HANDLER_CLASS eclipselink.exception-handler This property can also be set on a composite persistence unit. The first <tt>ExceptionHandler specified by a member handles the exception. If it is not specified or fails, then the composite's ExceptionHandler handles the original exception.
INCLUDE_DESCRIPTOR_QUERIES eclipselink.session.include.descriptor.queries
ID_VALIDATION eclipselink.id-validation
TEMPORAL_MUTABLE eclipselink.temporal.mutable
ORM_SCHEMA_VALIDATION eclipselink.orm.validate.schema
DDL_*
PESSIMISTIC_LOCK_TIMEOUT javax.persistence.lock.timeout
QUERY_TIMEOUT javax.persistence.query.timeout
ORACLE_PROXY_TYPE eclipselink.oracle.proxy-type


Entity Manager Properties

As always, Entity Manager properties can be set either through either createEntityManager() method on the factory or to the setProperty method on the EntityManager.

Example

Property ""eclipselink.jdbc.exclusive-connection.mode"" passed to the composite persistence unit, connection properties passed to the member persistence units through "eclipselink.composite-unit.properties" property.

Map props1 = new HashMap();
 
   props1.put("javax.persistence.jdbc.user", "user1");
   props1.put("javax.persistence.jdbc.password", "password1");
   props1.put("javax.persistence.jdbc.driver", "oracle.jdbc.OracleDriver");
   props1.put("javax.persistence.jdbc.url", "jdbc:oracle:thin:@oracle_db_url:1521:db");
 
Map props2 = new HashMap();
 
   props2.put("javax.persistence.jdbc.user", "user2");
   props2.put("javax.persistence.jdbc.password", "password2");
   props2.put("javax.persistence.jdbc.driver", "com.mysql.jdbc.Driver");
   props2.put("javax.persistence.jdbc.url", " jdbc:mysql://my_sql_db_url:3306/user2");
 
Map memberProps = new HashMap();
   memberProps.put("memberPu1", props1);
   memberProps.put("memberPu2", props2);
 
Map props = new HashMap();
   props.put("eclipselink.jdbc.exclusive-connection.mode", "Always");
   props.put("eclipselink.composite-unit.properties", memberProps);
 
EntityManager em = emf.createEntityManager(props);

The following tables show where to set properties: on the composite persistence unit or on the composite member persistence unit.

For complete PersistenceUnitProperties reference documentation, see [|EntityManagerProperties].

Entity Manager Properties That Can Be Set On Composite Persistence Units

You can set the following entity manager properties on composite persistence units. All other properties will be ignored.

EntityManagerProperties. Property Name
COMPOSITE_PROPERTIES eclipselink.composite.properties
FLUSH_CLEAR_CACHE eclipselink.flush-clear.cache
VALIDATE_EXISTENCE eclipselink.validate-existence
JOIN_EXISTING_TRANSACTION eclipselink.transaction.join-existing
PERSISTENCE_CONTEXT_* eclipselink.persistence-context.*
ORDER_UPDATES eclipselink.order-updates

Entity Manager Properties That Can Be Set On Composite Member Persistence Units

You can set the following entity manager properties on composite member persistence units. All other properties will be ignored.

EntityManagerProperties. Property Name
EXCLUSIVE_CONNECTION_* eclipselink.jdbc.exclusive-connection.*
JDBC_DRIVER javax.persistence.jdbc.driver
JDBC_URL javax.persistence.jdbc.url
JDBC_USER javax.persistence.jdbc.user
JDBC_PASSWORD javax.persistence.jdbc.password
JTA_DATASOURCE javax.persistence.jtaDataSource
NON_JTA_DATASOURCE javax.persistence.nonJtaDataSource
CONNECTION_POLICY eclipselink.jdbc.connection-policy
ORACLE_PROXY_TYPE eclipselink.oracle.proxy-type

Deploying and Accessing a Composite Persistence Unit

All the jars – the composite and the members – should be deployed on the same class loader. If they are deployed to an application server, the jars should be packed in an ear file. If they run standalone, the jars should be added to the class path.

A composite persistence unit can be accessed as any other persistence unit.

  • Container managed composite persistence unit could be accessed using injection:
@PersistenceUnit(unitName="compositePu")
EntityManagerFactory entityManagerFactory;
@PersistenceUnit(unitName="compositePu")
EntityManager entityManager;
EntityManagerFactory entityManagerFactory = Persistence.createEntityManagerFactory("compositePu", properties);

Limitations

Composite members persistence units' names must be unique in the composite.

Joins across tables in different data sources are not supported. This limitation affects mapping, query execution, and optimizations. For example:

  • Entities mapped in different composite members cannot be joined in a query.
  • If deleting an entity causes deletion from a table that is mapped by another composite member, then a "delete all" query cannot be performed. Therefore a delete all cannot be used if an entity:
    • has ElementCollection mapped in another composite member,
    • owns bidirectional relationship with a JoinTable with the target mapped in another composite member,
    • has any reference mapping that is privately owned with the target mapped in another composite member.

The inheritance hierarchy cannot be shared between different composite members.

If the target of a reference mapping is defined in a different composite member and JoinTable is used, the join table must belong to the target composite member. Such mappings must be unidirectional: the "invert" mapping cannot use mappedBy. That is because JoinTable must be defined in the same composite member with the target entity. Master mapping requires it to be in slave's member, slave mapping - in master's.You can work around this limitation by defining independent invert mapping with its own JoinTable. If you maintain both sides of the relationship, the two join tables will be in sync.

A native query created without a result class must specify the target composite member persistence unit, for example:

em.createNativeQuery("SELECT F_NAME FROM MBR2_EMPLOYEE").setHint(QueryHints.COMPOSITE_UNIT_MEMBER, "composite-advanced-member_2").getResultList();

Extensions

You can specify ElementCollection with primitive type target values with CollectionTable defined in a different composite member persistence unit, using annotations or eclipselink-orm.xml as described below:

  • Annotations
@ElementCollection()
@CollectionTable(name = "MBR1_RESPONS", joinColumns=@JoinColumn(name="EMP_ID"))
@CompositeMember("composite-advanced-member_1")
@Column(name = "DESCRIPTION")
public Collection<String> getResponsibilities() {
    return responsibilities;
}
  • eclipselink-orm.xml
<element-collection name="responsibilities" composite-member="xml-composite-advanced-member_3">
    <column name="DESCRIPTION"/>
    <collection-table name="XML_MBR3_RESPONS">
        <join-column name="EMP_ID"/>
    </collection-table>
</element-collection>

No @CompositeMember annotation (or composite-member attribute) is required if CollectionTable is defined in the same composite member persistence unit as the source.