[javaee-spec users] Re: "Distinct and non-overlapping" context roots

From: Edward Burns <>
Date: Fri, 25 Mar 2016 10:36:50 -0700

>>>>> On Thu, 17 Mar 2016 19:10:56 +0000 (UTC), PB said:

PB> Dear EG Members,
PB> I'd like to get clarification in regards to the following. I am quoting
PB> from EE 5.0 (see link below), section 8.3.1, paragraph 3c. This
PB> language still exists in EE 7 and dates back to at least EE 1.3:

PB> The Deployer must... "Assign a context root for each web module
PB> included in the Java EE application. The context root is a relative
PB> name in the web namespace for the application. Each web module must be
PB> given a distinct and non-overlapping name for its context root."

PB> This scenario I have today:
PB> /context/something <-- context is /context
PB> /context/something/somethingelse <-- context is /context/something

PB> Please advise on these points:

PB> a) The specification puts no limitations on the context root character
PB> set (so it can include a slash). With that said, would you consider
PB> these "overlapping" contexts as the specification defines it?

I have filed <>.

PB> b) What does the language "web namespace for the application" really
PB> mean? If I take "application" to mean EAR, it sounds like this
PB> restriction is only within an EAR; yet I am puzzled why the restriction
PB> isn't meant for the entire application server.

>>>>> On Mon, 21 Mar 2016 10:59:23 -0700, B said:

B> b) Yes, this restriction is only within the EAR. The reference
B> implementation (GlassFish) imposes this for the entire server.
B> The Servlet spec should probably require that.


B> d) The rule only applies for multiple web modules in an EAR file.
B> As in (b), it probably should apply to the entire server.

I have filed <>.


| | office: +1 407 458 0017