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:
Context
!-- Default set of monitored resources --
From: Ken Bowen [mailto:kbo...@als.com]
Subject: Re: [Solved+Question]SessionListener not being invoked
Context path= debug=5 reloadable=true crossContext=true
Note that the path attribute is not allowed (if your Context element is in a
standard location), and the debug attribute hasn't
]
Subject: Re: [Solved+Question]SessionListener not being invoked
Context path= debug=5 reloadable=true crossContext=true
Note that the path attribute is not allowed (if your Context
element is in a standard location), and the debug attribute hasn't
been used in some years. Use conf
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
complaint when Tomcat starts the app?
Unfortunately
.
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). Should I
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 believe Context elements had
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 life inside
conf/server.xml.
Once upon
