An exploded war inside an archived ear returns 404 in EAP 6

Solution Verified - Updated -

Issue

When an archived EAR which includes an exploded WAR is deploy in EAP6, the application seems to be deployed successfully but it returns status code 404. The same application works in EAP5. And, If an application is an exploded EAR which includes an exploded WAR, it works in EAP6.

Is this a bug? Or such a deployment, an exploded war inside an archived ear, is not supported in EAP6?

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6.0.x
    • 6.1.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content