Context-Root of WAR cannot be changed if WAR is not in root of EAR

[hades32]

This was closed on GitHub, but I think that this is a bug.

I created a

Working example: (snippets from META-INF/application.xml in an EAR)

  <module id="wftest.server-wftest.server.backend.web">
    <web>
      <web-uri>wftest.server-wftest.server.backend.web-1.31.0-buildr.war</web-uri>
      <context-root>/eu/backend</context-root>
    </web>
  </module>

NOT working example: (the WAR file was moved into /war of course beforehand)

  <module id="wftest.server-wftest.server.backend.web">
    <web>
      <web-uri>war/wftest.server-wftest.server.backend.web-1.31.0-buildr.war</web-uri>
      <context-root>/eu/backend</context-root>
    </web>
  </module>

The second form is the default of what buildr (https://buildr.apache.org/packaging.html#ear) produces. It can be worked around with something like `, :path=>''`, but why the limitation? For me this looks like a bug.

Tested with Wildfly 9.0 Final

[ctomc]

Hey,

it does look like a bug, can you create jira for this and if possible provide a simple reproducer for it.

thank you.

[jaikiran]

I vaguely remember there was a JIRA for this. Will try and find that one.

[jaikiran]

jaikiran wrote:

I vaguely remember there was a JIRA for this. Will try and find that one.

This is the one I was talking about https://issues.jboss.org/browse/WFLY-29 which has been marked as resolved in 8.x. So if it's still reproducible, then yes, like Tomaz noted, please create a new JIRA and add relevant details to it.

[hades32]

Actually the issue is slightly different. My ear can be deployed. The problem is only that the setting of the context-root doesn't work.

So in my example it is "/wftest.server-wftest.server.backend.web-1.31.0-buildr" instead of "/eu/backend". But I'll open an issue.

[ctomc]

ah that is different story all together.

do you maybe have jboss-web.xml in WEB-INF folder of your war?

also can you post full server.log(attach file using advanced editor) when your app is deploying