Caldarale, Charles R wrote:
>> From: Ken Bowen [mailto:kbo...@als.com]
>> Subject: Re: [Solved+Question]SessionListener not being invoked
>>
>> This project has been sputtering along for a fair number of
>> years, and my context.xml almost certainly began
> From: Ken Bowen [mailto:kbo...@als.com]
> Subject: Re: [Solved+Question]SessionListener not being invoked
>
> This project has been sputtering along for a fair number of
> years, and my context.xml almost certainly began life inside
> conf/server.xml.
Once upon a time, I bel
e now.
Cheers,
Ken
On Dec 3, 2009, at 11:02 PM, Caldarale, Charles R wrote:
From: Ken Bowen [mailto:kbo...@als.com]
Subject: Re: [Solved+Question]SessionListener not being invoked
One question: What does it mean to say "the path attribute is not
allowed"? (My context.xml is in META-INF
> From: Ken Bowen [mailto:kbo...@als.com]
> Subject: Re: [Solved+Question]SessionListener not being invoked
>
> One question: What does it mean to say "the path attribute is not
> allowed"? (My context.xml is in META-INF). Should I be seeing a
> complain
..@als.com]
Subject: Re: [Solved+Question]SessionListener not being invoked
Note that the path attribute is not allowed (if your
element is in a standard location), and the debug attribute hasn't
been used in some years. Use conf/logging.properties to set the
desired logging level.
> From: Ken Bowen [mailto:kbo...@als.com]
> Subject: Re: [Solved+Question]SessionListener not being invoked
>
>
Note that the path attribute is not allowed (if your element is in a
standard location), and the debug attribute hasn't been used in some years.
Use conf/logging.
Chris,
This seems to be the source of the problem. Just to be sure I'm on
target, I'll run through
a few details, and then I have a follow-on question. My tomcat-6.0.20/
conf/context.xml is the
one shipped with the download:
WEB-INF/web.xml
And the app-
