Does anyone know of a mechanism to determine which servlet will be ultimately invoked for the current request within a filter? I originally thought that FilterChain would have it but no go. I'm using Servlet API v2.3.
I'm looking at converting some earlier version 2.0 servlet code to extract common logic into filters and I want to minimise differences in logging etc. I'll probably throw away the linkage at some point but as an interim step small is generally better :-)
Michael Rutherfurd
WARNING - This email and any attachments may be confidential. If received in error, please delete and inform us by return email. Because emails and attachments may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems, you must be cautious. Westpac cannot guarantee that what you receive is what we sent. If you have any doubts about the authenticity of an email by Westpac, please contact us immediately. It is also important to check for viruses and defects before opening or using attachments. Westpac's liability is limited to resupplying any affected attachments. Westpac Banking Corporation ABN is 33 007 457 141. |
Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
