[
https://issues.jboss.org/browse/AS7-2505?page=com.atlassian.jira.plugin.s...
]
Abhi S updated AS7-2505:
------------------------
Description:
If an application is packaged with MDBs and RAs (resource adapters) such that the order of
deployment of these modules needs to be deterministic, the application fails to load. In
other words, there is no way to define the order in which MDBs and RAs must be loaded in
an application. This is a strict requirement by JEE 6, and without this support, JBoss 7
cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
was:
If an application is packaged with MDBs and RAs (resource adapters) such that the order of
deployment of these modules needs to be deterministic, the application fails to load. In
other words, there is no way to define the order in which MDBs and RAs must be loaded in
an application. This is a strict requirement by JEE 6, and without this support, JBoss 7
cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB.
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
Deployment order for MDBs and RAs is not working for a packaged EAR
-------------------------------------------------------------------
Key: AS7-2505
URL:
https://issues.jboss.org/browse/AS7-2505
Project: Application Server 7
Issue Type: Bug
Components: Deployment, EJB, JCA
Affects Versions: 7.0.2.Final, 7.1.0.Alpha1
Environment: Windows 7 64-bit
Reporter: Abhi S
Assignee: Thomas Diesler
Priority: Critical
Labels: deployment, ear, mdb, ra
Attachments: jee-app.ear
If an application is packaged with MDBs and RAs (resource adapters) such that the order
of deployment of these modules needs to be deterministic, the application fails to load.
In other words, there is no way to define the order in which MDBs and RAs must be loaded
in an application. This is a strict requirement by JEE 6, and without this support, JBoss
7 cannot be fully JEE 6 compliant.
Theoretically, following are 3 different ways to accomplish the above objective:
# Set <initialize-in-order> to true; see
http://java.sun.com/xml/ns/javaee/application_6.xsd. This seems to be fixed in AS7-325,
but I tested it using a sample application, and this definitely does not work for MDBs and
RAs.
# Add jboss-ejb3.xml in the MDB jar's MATA-INF to define the MDB's dependency on
an RA. Adding this configuration MUST ensure that the application loader loads the RA
before trying to load the MDB. Development of this feature is still in progress
(AS7-1211).
# Add org.jboss.ejb3.annotation.Depends annotation on the MDB implementation, to do the
same as #2.
None of the above work in the nightly build of AS7.1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira