[jboss-jira] [JBoss JIRA] (JBAS-8767) Startup fails if a web-fragment.xml references fragment name that's not present

[Jason Peng (JIRA)]

    [ https://issues.jboss.org/browse/JBAS-8767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13031613#comment-13031613 ] 

Jason Peng commented on JBAS-8767:
----------------------------------

Hi there,
i recently found the same exception on EAP 6.3. I'm wondering if the behaviour of AS being changed to terminate init process or bypass the unknown name?
(Restricted to jira-users group)
> 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: Application Server 3  4  5 and 6
>          Issue Type: Bug
>          Components: Web (Tomcat) service
>    Affects Versions: 6.0.0.CR1
>            Reporter: Dan Allen
>            Assignee: Remy Maucherat
>            Priority: Blocker
>             Fix For: 6.0.0.Final
>
>         Attachments: webfragref.war
>
>
> 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 was sent by Atlassian JIRA
(v6.3.11#6341)