[seam-issues] [JBoss JIRA] (JBSEAM-4856) AS7 Multi-war ear Seam 2.2.2.Final fails deployment (race condition?)

[ https://issues.jboss.org/browse/JBSEAM-4856?page=com.atlassian.jira.plugi... ] Marek Novotny edited comment on JBSEAM-4856 at 1/27/12 10:35 AM: ----------------------------------------------------------------- I was exploring the issue also from other point of view and found out proper workaround without changing source code in Seam, but not sure if that is what it should be as an result of this issue ;-). So in meanwhile this works for me on attached test case and on the latest 2.3.0-SNAPSHOT * I tried to add {noformat}<ear-subdeployments-isolated>true</ear-subdeployments-isolated> {noformat} into jboss-deployment-structure.xml file * Second rewrote the generation of EAR's application.xml in EAR pom.xml to be Java EE 6 specific and {code:xml} <plugin> <artifactId>maven-ear-plugin</artifactId> <version>2.6</version> <configuration> <version>6</version> <generateApplicationXml>true</generateApplicationXml> <defaultLibBundleDir>lib</defaultLibBundleDir> <initializeInOrder>true</initializeInOrder> <modules> <jarModule> <groupId>org.jboss.el</groupId> <artifactId>jboss-el</artifactId> <includeInApplicationXml>false</includeInApplicationXml> <bundleDir>lib</bundleDir> </jarModule> <ejbModule> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam</artifactId> <bundleFileName>jboss-seam.jar</bundleFileName> </ejbModule> <ejbModule> <groupId>dk.lungogbendsen.seam</groupId> <artifactId>seam-hello-ejbs</artifactId> <bundleFileName>seam-hello-jbs.jar</bundleFileName> </ejbModule> <webModule> <groupId>dk.lungogbendsen.seam</groupId> <artifactId>seam-hello-web1</artifactId> <contextRoot>/seam-hello1</contextRoot> <bundleFileName>seam-hello-web1.war</bundleFileName> </webModule> <webModule> <groupId>dk.lungogbendsen.seam</groupId> <artifactId>seam-hello-web2</artifactId> <contextRoot>/seam-hello2</contextRoot> <bundleFileName>seam-hello-web2.war</bundleFileName> </webModule> </modules> </configuration> </plugin> {code} was (Author: manaRH): I was exploring the issue also from other point of view and found out proper workaround without changing source code in Seam, but not sure if that is what it should be as an result of this issue ;-). So in meanwhile this works for me on attached test case and on the latest 2.3.0-SNAPSHOT * I tried to add {noformat}<ear-subdeployments-isolated>false</ear-subdeployments-isolated> {noformat} into jboss-deployment-structure.xml file * Second rewrote the generation of EAR's application.xml in EAR pom.xml to be Java EE 6 specific and {code:xml} <plugin> <artifactId>maven-ear-plugin</artifactId> <version>2.6</version> <configuration> <version>6</version> <generateApplicationXml>true</generateApplicationXml> <defaultLibBundleDir>lib</defaultLibBundleDir> <initializeInOrder>true</initializeInOrder> <modules> <jarModule> <groupId>org.jboss.el</groupId> <artifactId>jboss-el</artifactId> <includeInApplicationXml>false</includeInApplicationXml> <bundleDir>lib</bundleDir> </jarModule> <ejbModule> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam</artifactId> <bundleFileName>jboss-seam.jar</bundleFileName> </ejbModule> <ejbModule> <groupId>dk.lungogbendsen.seam</groupId> <artifactId>seam-hello-ejbs</artifactId> <bundleFileName>seam-hello-jbs.jar</bundleFileName> </ejbModule> <webModule> <groupId>dk.lungogbendsen.seam</groupId> <artifactId>seam-hello-web1</artifactId> <contextRoot>/seam-hello1</contextRoot> <bundleFileName>seam-hello-web1.war</bundleFileName> </webModule> <webModule> <groupId>dk.lungogbendsen.seam</groupId> <artifactId>seam-hello-web2</artifactId> <contextRoot>/seam-hello2</contextRoot> <bundleFileName>seam-hello-web2.war</bundleFileName> </webModule> </modules> </configuration> </plugin> {code} -- 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