11:55 p.m.
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Scott Marlow
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:22 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on JBAS-9155:
------------------------------------
Vincent,
Thank you for reporting this issue. Would you be interested in helping to write a test
case for AS7 that reproduces the above structure? I can provide guidance for putting it
together if your interested.
If your interested in helping. I can give you the steps to get the AS7 source and such a
test in AS7.
The test could likely go in a new
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/src...
folder.
Another example test is here
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/src...
All of the classes in the epcpropagation/ folder are part of the test.
Some other examples of how a test case packages up the test classes into archives are
here:
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/src...
https://github.com/jbossas/jboss-as/blob/master/testsuite/integration/src...
Don't worry so much about the obstacles of getting the source and contributing the
test.
What do you think?
Thanks,
Scott
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Scott Marlow
Labels: deployment, jboss, jpa, persistence, war
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:50 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Vincent A commented on JBAS-9155:
---------------------------------
Hi Scott,
I'd be happy to write a test case if you point me in the right direction.
I ran a quick test on AS 7 Beta1; both perstistence.xml are read:
{code}
22:11:54,212 INFO [org.jboss.jpa] (MSC service thread 1-4) read persistence.xml for pu1
22:11:54,213 INFO [org.jboss.jpa] (MSC service thread 1-4) read persistence.xml for pu2
{code}
I'm not sure they're both started though.
-vincent
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Scott Marlow
Labels: deployment, jboss, jpa, persistence, war
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:26 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on JBAS-9155:
------------------------------------
Hi Vincent,
I look forward to working with you on that. I'll work on some notes to guide how it
can be done and add a link to them here.
Scott
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Scott Marlow
Labels: deployment, jboss, jpa, persistence, war
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:03 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Scott Marlow edited comment on JBAS-9155 at 4/5/11 1:02 PM:
------------------------------------------------------------
To get started with creating a test case, get started with using git and the AS7 source
repository at https://github.com/jbossas/jboss-as/
Some guidance with getting started is here: http://community.jboss.org/wiki/HackingonAS7
If you look at SessionFactoryTestCase.java in the following source tree (see contents of
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/src...).
You will see a reasonably simple test case that could be cloned).
Also look at the other example nearby in
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/src...
More details are in
http://community.jboss.org/wiki/WritingaAS7TestCaseintestsuitemodule...
was (Author: smarlow):
To get started with creating a test case, get started with using git and the AS7
source repository at https://github.com/jbossas/jboss-as/
Some guidance with getting started is here: http://community.jboss.org/wiki/HackingonAS7
If you look SessionFactoryTestCase.java in the following source tree (see contents of
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/src...).
You will see a reasonably simple test case that could be cloned).
Also look at the other example nearby in
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/src...
More details are in
http://community.jboss.org/wiki/WritingaAS7TestCaseintestsuitemodule...
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Scott Marlow
Labels: deployment, jboss, jpa, persistence, war
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:03 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on JBAS-9155:
------------------------------------
To get started with creating a test case, get started with using git and the AS7 source
repository at https://github.com/jbossas/jboss-as/
Some guidance with getting started is here: http://community.jboss.org/wiki/HackingonAS7
If you look SessionFactoryTestCase.java in the following source tree (see contents of
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/src...).
You will see a reasonably simple test case that could be cloned).
Also look at the other example nearby in
https://github.com/jbossas/jboss-as/tree/master/testsuite/integration/src...
More details are in
http://community.jboss.org/wiki/WritingaAS7TestCaseintestsuitemodule...
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Scott Marlow
Labels: deployment, jboss, jpa, persistence, war
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:36 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
David Lloyd updated JBAS-9155:
------------------------------
Fix Version/s: 6.1.0
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Scott Marlow
Labels: deployment, jboss, jpa, persistence, war
Fix For: 6.1.0
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:03 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Shelly McGowan commented on JBAS-9155:
--------------------------------------
Does this issue correctly identify the Fix For version? It's identified to be Resolved
in AS 6.1.0 but the discussion is about AS 7? Scott/Vincent can you clarify?
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Scott Marlow
Labels: deployment, jboss, jpa, persistence, war
Fix For: 6.1.0
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:19 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Scott Marlow commented on JBAS-9155:
------------------------------------
The AS 7 discussion, was really for AS 7. It seems that we ran out of time for fixing the
reported AS 6.0 issue (not fixed for 6.1).
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Scott Marlow
Labels: deployment, jboss, jpa, persistence, war
Fix For: 6.1.0
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:27 p.m.
New subject: [JBoss JIRA] Assigned: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Shelly McGowan reassigned JBAS-9155:
------------------------------------
Assignee: Ales Justin (was: Scott Marlow)
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Ales Justin
Labels: deployment, jboss, jpa, persistence, war
Fix For: 6.1.0
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
noon
New subject: [JBoss JIRA] Resolved: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Shelly McGowan resolved JBAS-9155.
----------------------------------
Resolution: Done
This was Resolved in AS 6.1.0.Final. If necessary, clone the issue for AS 7.
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Ales Justin
Labels: deployment, jboss, jpa, persistence, war
Fix For: 6.1.0
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
noon
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-9155) jboss processes only one persistence.xml file per war file
[
https://issues.jboss.org/browse/JBAS-9155?page=com.atlassian.jira.plugin....
]
Shelly McGowan edited comment on JBAS-9155 at 8/15/11 12:58 PM:
----------------------------------------------------------------
The AS 7 discussion, was really for AS 7.
was (Author: smarlow):
The AS 7 discussion, was really for AS 7. It seems that we ran out of time for fixing
the reported AS 6.0 issue (not fixed for 6.1).
jboss processes only one persistence.xml file per war file
-----------------------------------------------------------
Key: JBAS-9155
URL: https://issues.jboss.org/browse/JBAS-9155
Project: Legacy JBoss Application Server 6
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: JPA / Hibernate
Affects Versions: 6.0.0.Final
Reporter: Vincent A
Assignee: Ales Justin
Labels: deployment, jboss, jpa, persistence, war
Fix For: 6.1.0
If a war file contains several Persistence Archive jars, JBoss starts only the persitence
unit(s) defined in the first jar it scans, ignoring the remaining ones.
For instance, given the following war file:
{code}
my-war
+-- WEB-INF
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>}}
{code}
Jboss will only starts the pu1 persistence unit.
And if the war file has the following structure:
{code}
my-war
+-- WEB-INF
+-- classes
+-- META-INF
+ persistence.xml // <persistence-unit name="pu0"
>...</persistence-unit>
+-- lib
+-- pu1.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu1"
>...</persistence-unit>
+-- pu2.jar
+-- META-INF
+ persistence.xml // <persistence-unit name="pu2"
>...</persistence-unit>
{code}
Jboss starts pu0, and skips the PU's defined in pu1.jar and pu2.jar.
This behaviour is non-compliant. Section 6.2 of the spec states that:
{quote}
A persistence unit may be packaged within one or more jar files
contained within a WAR or EAR, as a set of classes within an
EJB-JAR file or in the WAR classes directory, or as a combination
of these as defined below.
{quote}
[...]
{quote}
It is not required that an EJB-JAR or WAR containing a persistence
unit be packaged in an EAR unless the persistence unit contains
persistence classes in addition to those contained in the EJB-JAR
or WAR.
{quote}
And from section 7:
{quote}
7.1.1 Responsibilities of the Container
At deployment time the container is responsible for scanning the
locations specified in Section 6.2 and discovering the persistence.xml
files and processing them.
When the container finds a persistence.xml file, it processes the
persistence unit definitions that it contains.
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4839
days inactive
4979
days old
11 comments
4 participants
participants (4)
-
David Lloyd (JIRA) -
Scott Marlow (JIRA)
-
Shelly McGowan (JIRA)
-
Vincent A (JIRA)