From: Mark Thomas <markt_at_apache.org>
Date: Wed, 2 Sep 2015 14:54:06 +0100
On 02/09/2015 13:01, arjan tijms wrote:
> Hi.
>
> On Wed, Sep 2, 2015 at 12:24 PM, Mark Thomas <markt_at_apache.org> wrote:
>> I'm aware of application.xml for EAR files. Pointers to the docs for
>> other containers would be appreciated since I don't know them at all.
>
> Just a couple of quick ones that weren't mentioned yet:
Thanks. Useful background. A couple of things popped out at me.
- None of the docs speak to how conflicts are handled if two WARs
specify the same path. If this feature is added to web.xml then the
specification needs to address this so the behaviour is consistent
across containers.
- Most seem to use it as a default (that takes precedence over the file
name) that can be overridden elsewhere in the deployment process
- The Jetty docs mention one of the pitfalls of this approach is that
changing it requires modifying the WAR although in the Jetty case that
looks to be because the value, if present, has precedence over other
options.
I can see the attraction of taking a configuration option that most
containers provide in some container specific way and providing a common
configuration option for it in web.xml.
However, I remain unconvinced that this feature is a good idea.