tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Funk <funk...@joedog.org>
Subject Re: Spec ambiguity? filters and request dispatching
Date Tue, 01 Oct 2002 19:27:06 GMT
This already has been discussed in the user group in these 2 threads. In 
a nutshell, tomcat is doing it correctly.

But I do find it interesting that websphere and weblogic do differ from 
tomcat in the same manner with respect to this issue.

http://archives2.real-time.com/pipermail/tomcat-users/2002-September/080829.html

http://archives2.real-time.com/pipermail/tomcat-users/2002-September/078864.html


Eddie Ruvinsky wrote:
> The Servlet Spec seems ambiguous about when exactly
> the servlet container should invoke filters.  Tomcat's
> behavior is for a filter to get invoked only when the
> request arrives, and before any servlets execute. 
> However, what should the correct behavior be when a
> servlet tries to include or forward a request using
> RequestDispatcher to another servlet that is
> configured to be "intercepted" by a filter?  Tomcat
> apparently does not invoke the filter [again] for any
> dispatched requests.  This is contrary to WebSphere's
> interpretation of the spec since it invokes filters
> even for dispatched requests (and leaves it up to the
> developer to check if the filter is called
> "recursively").  This difference in behavior between
> servers certainly leads to non-portable applications,
> so it should be addressed.
> 
> I'm not sure if this is off-topic for this email
> group, but I thought I'd start here since Tomcat is
> the reference implementation of the spec.
> 
> Thanks,
> -Eddie
>  


--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message