There's the rub. You don't. But you can inspect
request.getServletPath()
OR
request attributes:
javax.servlet.include.request_uri
javax.servlet.include.context_path
javax.servlet.include.servlet_path
javax.servlet.include.path_info
javax.servlet.include.query_string
javax.servlet.forward.request_uri
javax.servlet.forward.context_path
javax.servlet.forward.servlet_path
javax.servlet.forward.path_info
javax.servlet.forward.query_string
To deduce the servlet called. So you can easily run logging on the servlet
path, but not the servlet class.
-Tim
Leon Rosenberg wrote:
Thanx tim,
I have one last question, which would be probably the hardest to answer...
How do I now _which_ servlet is behind me in the chain?
regards
Leon
On 5/26/06, Tim Funk <[EMAIL PROTECTED]> wrote:
Yes you will ...
doFilter(...) {
// log and set other timing variables
try {
chain.doFilter(...)
} finally {
/*
servlet done executing - log some more
*/
}
}
If the filter is invoked on includes and forwards too - you can also
get more
granually logging.
-Tim
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
