[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4166) Seam Web EAR project using Seam 2.1.1.GA does not work on JBoss AS 4.2.3

[ https://jira.jboss.org/jira/browse/JBIDE-4166?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-4166: -------------------------------------------- http://lists.jboss.org/pipermail/jboss-development/2009-April/014319.html shows the full thread that explains the workaround: "So the *workaround* is to ensure that deployments which are referenced in Classpath attribute of other deployments are deployed first. For ex: in the application attached to the JIRA, the xxx-ejb.jar refers to jboss-seam.jar (EJB deployment) in the MANIFEST.MF. So the trick is to ensure that jboss-seam is picked up for deployment before xxx-ejb.jar is picked for deployment (and the subsequent MANIFEST.MF processing). This can be done by specifying the correct order of modules in the application.xml and *also* specifying the module-order as "strict" in jboss-app.xml (by default the module-order is "implicit" which follows filename based deployment ordering [2]). So here's what i did: application.xml: <?xml version="1.0" encoding="UTF-8"?> <application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd" version="5"> <display-name>xxx-ear</display-name> <!-- JBIDE-4166 Workaround - Make sure we deploy this first, since this is referenced in xxx-ejb.jar--> <module> <ejb>jboss-seam.jar</ejb> </module> <module> <ejb>xxx-ejb.jar</ejb> </module> <module> <web> <web-uri>xxx.war</web-uri> <context-root>/xxx</context-root> </web> </module> </application> jboss-app.xml: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 4.2//EN" "http://www.jboss.org/j2ee/dtd/jboss-app_4_2.dtd"> <jboss-app> <!-- JBIDE-4166 : We need strict ordering to follow the order mentioned in application.xml --> <module-order>strict</module-order> <loader-repository> seam.jboss.org:loader=xxx-ear.ear </loader-repository> </jboss-app> So all that JBoss Tools needs to do is add a intelligent ordering of the modules in the application.xml and mark the application for strict module ordering in the jboss-app.xml. [1] http://anonsvn.jboss.org/repos/jbossas/tags/JBoss_4_2_3_GA/system/src/mai... [2] This also explains why the deployment behaves differently when the name of the deployment is changed." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira