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.
secretdark wrote :
|
| If I then deploy an EAR containing a similiar WAR with the same context
(i.e. /static) it is then overridden.
|
That's changed (read handled correctly) in JBossAS-5.0.x, where multiple
applications are not allowed to have the same context. Which AS version do
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=bbop=viewtopicp=4225577#4225577
Reply to the post :
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,
By path do you mean web app context? If so, if there is already an app that
is using the context /xxx then deploying a new app with the same context will
fail.
If you don't mean 'context', what do you mean by 'path'?
View the original post :
