Likewise, are context paths allowed to be shared? For example, if I deploy a
EAR with a context path of:
/application
which contains a subdirectory named 'static' i.e.
/application/static
And I then deploy a WAR containing simply a modified verison of the directory
and the same sub-context path,
We're currently using 4.2.2. and, unfortunately, an upgrade is not an option at
the moment. I take it that this is the expected behaviour for this version then?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225577#4225577
Reply to the post :
http://www.jbos
Thanks for the response.
The context of the WAR I'm deploy ends up being:
/static
If I then deploy an EAR containing a similiar WAR with the same context (i.e.
/static) it is then overridden. Is there any method of defining what deployment
would take precedence beyond simply timestamp (i.e. la
Hi,
I'm have a question regarding the precedence of deployment paths. Specifically,
if I was to deploy a WAR file with a specified path (for example, /newHTML)
alongside a already deployed EAR file with a path specified as the same
(/newHTML) would the precedence simply be given to the last dep
