Yes, I gave them the same example I used here. They confirmed it is "overlapping". Here is the example again:
/context/something <-- context is /context /context/something/somethingelse <-- context is /context/something Cheers, Paul On Tue, Mar 22, 2016 at 11:34 AM, David kerber <dcker...@verizon.net> wrote: > On 3/22/2016 12:31 PM, Paul Benedict wrote: > >> Mark, I did get some clarification. Thanks for asking. >> >> The EE spec states an "application" may not have overlapping context >> roots. >> I got clarification that "application" refers only to an EAR. Therefore, >> an >> EE server should be validating this condition. >> > > I've been following this thread just a bit, and have a question about it: > what does "overlapping" mean to them? To me, if one was a subset > (completely contained inside) of another one, that would not be > overlapping. Overlapping would imply that two apps would both match some > URLs, while other URLs would only match one or the other. Is that how they > define overlapping? > >