Startup fails if a web-fragment.xml references fragment name that's not present ------------------------------------------------------------------------------- Key: JBAS-8767 URL: https://issues.jboss.org/browse/JBAS-8767 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: 6.0.0.CR1 Reporter: Dan Allen Assignee: Remy Maucherat Fix For: 6.0.0.Final Application deployment should not fail if a web-fragment.xml references another fragment by name that isn't part of the deployment. That defeats the whole purpose of the relative ordering in the web-fragment.xml. For example, Seam Servlet needs to be ordered after Weld Servlet. So we define ordering the Seam Servlet web-fragment.xml as follows: <ordering> <after> <name>WeldServlet</name> </after> <before> <others/> </before> </ordering> However, we can't guarantee that Weld Servlet will be used. In that case, JBoss AS should just ignore the request. Here's the error that's appearing in the log: org.jboss.deployers.spi.DeploymentException: Invalid ordering Caused by: java.lang.IllegalStateException: Unknown name declared in JAR: seam-servlet-3.0.0-20101222.050701-2.jar at org.jboss.web.deployers.MergedJBossWebMetaDataDeployer.resolveOrder(MergedJBossWebMetaDataDeployer.java:711) [:6.0.0-SNAPSHOT] at org.jboss.web.deployers.MergedJBossWebMetaDataDeployer.deploy(MergedJBossWebMetaDataDeployer.java:306) [:6.0.0-SNAPSHOT] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira