Fix scope visibility of orm.xml when it is packaged in both ear file and war
file
---------------------------------------------------------------------------------
Key: OPENJPA-1460
URL: https://issues.apache.org/jira/browse/OPENJPA-1460
Project: OpenJPA
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Fay Wang
Assignee: Fay Wang
Fix For: 2.0.0
Per JPA 2.0 spec, section 8.2.2:
An EJB-JAR, WAR, application client jar, or EAR can define a persistence unit.
When referencing a persistence unit using the unitName annotation element or
persistence-unit-name deployment descriptor element, the visibility scope of
the persistence unit is determined by its point of definition:
(1) A persistence unit that is defined at the level of an EJB-JAR, WAR, or
application client jar is scoped to that EJB-JAR, WAR, or application jar
respectively and is visible to the components defined in that jar or war.
(2) A persistence unit that is defined at the level of the EAR is generally
visible to all components in the application. However, if a persistence unit of
the same name is defined by an EJB-JAR, WAR, or application jar file within the
EAR, the persistence unit of that name defined at EAR level will not be visible
to the components defined by that EJB-JAR, WAR, or application jar file unless
the persistence unit reference uses the persistence unit name # syntax to
specify a path name to disambiguate the reference. When the # syntax is used,
the path name is relative to the referencing application component jar file.
For example, the syntax ../lib/persistenceUnitRoot. jar#myPersistenceUnit
refers to a persistence unit whose name, as specified in the name element of
the persistence.xml file, is myPersistenceUnit and for which the relative path
name of the root of the persistence unit is ../lib/persistenceUnitRoot. jar.
The # syntax may be used with both the unitName annotation
element
or persistence-unit-name deployment descriptor element to reference a
persistence unit defined at EAR level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
