Doug, Read your mail on this. Can you elucidate on filters and listeners some more based on your experience? Say, advantages of using a filter instead of a listener? Will appreciate your insights.. Thanks
-----Original Message----- From: Srofe, Douglas (c) [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 10, 2002 2:11 PM To: 'Tomcat Users List' Subject: RE: Managing a Listener Craig, I have had some of the same issues to deal with. I accomplished this using a filter instead of a listener. The reason I used a filter is because it had access to the request and response information. A listener only had access to the session. For config information I used a class I wrote and obtained via a built-in JNDI resource. The class contained a static hash table that I populated with individual session (i.e. web app) information. I configured the filter to only look at requests of .jsp or servlets, otherwise everything comes through the filter (graphic requests, html, etc. If this is not enough to get you started, I would be happy to fill in some more specifics. Doug Srofe WDS interaktiv ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (Whitehouse Station, New Jersey, USA) that may be confidential, proprietary copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by e-mail and then delete it. ============================================================================== -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
