[jboss-jira] [JBoss JIRA] (WFLY-2028) An exploded war inside an archived ear returns 404

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on WFLY-2028:
-----------------------------------------------

Emmanuel Hugonnet (ehsavoie) <ehugonne at redhat.com> made a comment on [bug 991244|https://bugzilla.redhat.com/show_bug.cgi?id=991244]

https://github.com/ehsavoie/wildfly/compare/WFLY-2028 for a view on the current fix for Wildfly
                
> An exploded war inside an archived ear returns 404
> --------------------------------------------------
>
>                 Key: WFLY-2028
>                 URL: https://issues.jboss.org/browse/WFLY-2028
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: EE
>    Affects Versions: 8.0.0.Alpha4
>            Reporter: Emmanuel Hugonnet
>            Assignee: Emmanuel Hugonnet
>
> When an archived ear which includes an exploded war is deployed in EAP 6, the application seems to be deployed successfully but it returns status code 404. 
> 1. Start EAP 6 standalone mode
> 2. Put the attached test.ear to $JBOSS_HOME/standalone/deployments
> 3. Access the web application
>     curl -v http://localhost:8080/test/index.jsp 
> JBoss returns status code 404.
> JBoss returns actual response of web application's content.
> Additional info:
> Same application works in EAP 5. When an application is an exploded ear which includes an exploded war, it works in EAP 6.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira