Hi,
On Mon, Aug 31, 2015 at 9:20 PM, Mark Thomas <markt_at_apache.org> wrote:
> I'm still not entirely comfortable with this. How would we resolve
> conflicts?
I agree that it can be an issue.
If I'm not mistaken then in case of resources it's a question of first
come first serve. The first application to be deployed that defines a
given name in java:global "wins". A second application gets an
exception because of a duplicate resource definition. There was some
discussion about this a while back on the Java EE list; should it
always be a definition exception, or is it okay if that second
application happened to define an identical resource, etc.
> For request URI I think a change of the default to UTF-8 with container
> specific ways to change the default would be sufficient.
UTF-8 as a default would surely be the better option. If there aren't
too many concerns about backwards compatibility then this would really
be great.
> Nope. <Connector URIEncoding="..." ... /> in server.xml
Ah, ok, that's the right one. Thanks.
Kind regards,
Arjan Tijms