RE: TC4 servlet filter behavior different from WLS7

2002-09-30 Thread Rob Worsnop
]] Sent: Friday, September 27, 2002 12:49 PM To: Tomcat Users List Subject: RE: TC4 servlet filter behavior different from WLS7 Hi, For example: I have a servlet /hello, which forwards to /hello.jsp. I have a filter that is mapped to /hello.jsp. Accessing /hello in WebLogic

RE: TC4 servlet filter behavior different from WLS7

2002-09-27 Thread Shapira, Yoav
Hi, For example: I have a servlet /hello, which forwards to /hello.jsp. I have a filter that is mapped to /hello.jsp. Accessing /hello in WebLogic will trigger the filter. That doesn't happen in Tomcat. It was my understanding that the tomcat behavior here is correct. This is because you have

RE: TC4 servlet filter behavior different from WLS7

2002-09-27 Thread Rob Worsnop
, September 27, 2002 12:49 PM To: Tomcat Users List Subject: RE: TC4 servlet filter behavior different from WLS7 Hi, For example: I have a servlet /hello, which forwards to /hello.jsp. I have a filter that is mapped to /hello.jsp. Accessing /hello in WebLogic will trigger the filter

Re: TC4 servlet filter behavior different from WLS7

2002-09-27 Thread Tim Funk
Users List Subject: RE: TC4 servlet filter behavior different from WLS7 Hi, For example: I have a servlet /hello, which forwards to /hello.jsp. I have a filter that is mapped to /hello.jsp. Accessing /hello in WebLogic will trigger the filter. That doesn't happen in Tomcat. It was my

RE: TC4 servlet filter behavior different from WLS7

2002-09-27 Thread Rob Worsnop
]] Sent: Friday, September 27, 2002 1:41 PM To: Tomcat Users List Subject: Re: TC4 servlet filter behavior different from WLS7 See section 6.1.1 of the Spec 2.3 When the container receives the incoming request, it takes the first filter instance in the list and calls its doFilter() method