I see that if the attribute path is present in the context.xml, you can
see NPE in Tomcat ->RealmBase as evidenced by
The presence of an unsupported attribute should not throwing a NPE in
the wrong places. :)
Anil Saldhana wrote:
Rémy Maucherat wrote:
> On Tue, Apr 21, 2009 at 3:32 AM, Anil Saldhana
> <Anil.Saldhana(a)redhat.com> wrote:
>
>>
https://jira.jboss.org/jira/browse/JBAS-6811 has a web application
>> attached
>> (lambda.war). It has a WEB-INF/context.xml with the following setting:
>>
>> =======
>> <?xml version="1.0" encoding="UTF-8"?>
>> <Context path="/probe" privileged="true">
>> </Context>
>> ================
>>
>> The expectation is that the context path is set to "/path"
>>
>> But the log shows:
>>
>> =================================
>> 20:00:49,297 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
>> 20:00:49,399 INFO [TomcatDeployment] deploy,
>> ctxPath=/lambda =====================================
>>
>> I think this is a bug.
>>
>
> Setting a path using a context.xml file is not supported in Tomcat
> either (only in server.xml Context elements, which are no longer in AS
> 5 since I think deployments should be done through the JBoss
> deployer).
>
> Rémy
Thanks for the clarification, Remy. So, context.xml provides
currently just the valve defs?