[jira] Closed: (MEAR-124) transitive ejb modules not added to application.xml in correct deployment order for Jboss 4.2.x

["Stephane Nicoll (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MEAR-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Nicoll closed MEAR-124.
--------------------------------

    Resolution: Not A Bug
      Assignee: Stephane Nicoll

No feedback from user.

> transitive ejb modules not added to application.xml in correct deployment order for Jboss 4.2.x
> -----------------------------------------------------------------------------------------------
>
>                 Key: MEAR-124
>                 URL: http://jira.codehaus.org/browse/MEAR-124
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.4.1
>            Reporter: Ulrich Roell
>            Assignee: Stephane Nicoll
>
> EJB module entries should be added according to their dependencies. Assume you have a multi-module maven project with two EJB modules EJB_A, EJB_B and one EAR module. EJB_A depends on EJB_B and only EJB_A is declared as a dependency inside the EAR module's POM. So if you want to use module-order = strict, EJB_B must be added before EJB_A to your application.xml. Otherwise is it very likely that the JBoss deployment will fail! A workaround is to declare both EJB_A and EJB_B manually add EJB_B before EJB_A. But with Maven's dependency mechanism this could be done dynamically.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira