8:32 p.m.
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.
9:17 p.m.
Correction: the context path expectation is "/probe".
Anil Saldhana 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.
11:14 p.m.
We are not parsing a pat attribute during the creation of the
ContextMetaData in AS5, so it would not be picked up. We are also not
parsing a privileged attribute, so it seems we missed some attributes
when the parsing of the metadata was moved into a deployer.
Anil Saldhana 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.
2:10 a.m.
I created a bug
https://jira.jboss.org/jira/browse/JBAS-6812
Scott Stark wrote:
We are not parsing a pat attribute during the creation of the
ContextMetaData in AS5, so it would not be picked up. We are also not
parsing a privileged attribute, so it seems we missed some attributes
when the parsing of the metadata was moved into a deployer.
Anil Saldhana 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.
>
8:47 a.m.
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
9:18 a.m.
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?
11:06 a.m.
I see that if the attribute path is present in the context.xml, you can
see NPE in Tomcat ->RealmBase as evidenced by
https://jira.jboss.org/jira/browse/JBAS-6811
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?
5720
days inactive
5720
days old
jboss-development@lists.jboss.org
6 comments
3 participants
participants (3)
-
Anil Saldhana -
Rémy Maucherat -
Scott Stark