Thanks. This project has been sputtering along for a fair number of
years, and my context.xml almost certainly began life inside conf/
server.xml. I would be fairly confident in betting that I moved it
out on earlier advice from you, but that I didn't clean it up then.
Well, I have 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). Should I be seeing a
complaint when Tomcat starts the app?
Unfortunately, Tomcat won't complain about it (although I think it
should). The path attribute is only valid when the <Context>
element is nested inside of a <Host> element in conf/server.xml -
which is very strongly discouraged. Using a path attribute in any
other circumstance is not permitted, but not diagnosed. At best, it
will confuse anyone looking at your configuration, possibly thinking
that something meaningful is being done with it.
- 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
