The usage of context.xml mentioned below is similar to case (iii) below.
The proposed <context-root> in web.xml provides a context-root for the
application.
(We can clarify that the default context-root is name of the application
if <context-root> is not present in the web.xml.)
This can still be overridden by (ii) and (iii) below if it is necessary.
Shing Wai Chan
On 8/25/15, 6:20 PM, Justin Lee wrote:
> I think web.xml is probably not the *greatest* place for that. It's a
> static resource embedded in the deployment artifact that people would
> have to explode to change and then rebundle. I've seen (and used)
> context.xml, e.g., to allow for simultaneous deployments of wars. I
> haven't found matching war names to context roots is really a problem
> for single deployments.
>
> On Tue, Aug 25, 2015 at 8:53 PM, Shing Wai Chan
> <shing.wai.chan_at_oracle.com <mailto:shing.wai.chan_at_oracle.com>> wrote:
>
> I am looking at https://java.net/jira/browse/SERVLET_SPEC-137
> (“Allow context root”)
>
> In Java EE ear application, one can configure the context-root in
> application.xml.
> For war, there is no such configuration in web.xml.
>
> Most servlet containers take default context-root = name of the
> applications.
> And there are different solutions to configure the context-root as
> follows:
> i) configure context-root through the proprietary descriptors.
> For instance glassfish-web.xml in GlassFish and weblogic.xml in
> WebLogic.
> ii) configure context-root at the time of deployment without
> editing descriptors in the war.
> iii) support the configuration of context-root “after” the
> deployment through administration tool.
>
> I am considering adding a context-root element in web.xml.
> Any comments?
>
> Shing Wai Chan
>
>
>
>
> --
> You can find me on the net at:
> http://antwerkz.com <http://antwerkz.com/> http://antwerkz.com/+
> http://antwerkz.com/twitter http://antwerkz.com/github