Thanks Chuck.
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?
--Ken
On Dec 3, 2009, at 10:42 PM, Caldarale, Charles R wrote:
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
been used in some years. Use conf/logging.properties to set the
desired logging level.
Is the simplest principled, patient, and gentle way of
suppressing session persistence for my particular app
to add the following Manager config element to my
webapp's context.xml?
<Manager pathname="" />
Yes, that is the documented and recommended way:
"Restart persistence may be disabled by setting this attribute to an
empty string."
The above quote is taken from:
http://tomcat.apache.org/tomcat-6.0-doc/config/manager.html
And if I wanted all apps to suppress persistence, then I would just
uncomment that in ~conf/context.xml.
Also true.
- Chuck
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE
PROPRIETARY MATERIAL and is thus for use only by the intended
recipient. If you received this in error, please contact the sender
and delete the e-mail and its attachments from all computers.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
