Okay, I got it. Actually, WebServices are deployed in the root context. You need to add a servlet filter on the root webapp not on the one owning the web service. That is definitely not a good way, that's why I created a JIRA few month ago.
https://issues.apache.org/jira/browse/OPENEJB-1529 What are you trying to achieve? May be you can use JAX-WS Handlers? Jean-Louis 2011/7/20 rnieto <[email protected]> > > Jean-Louis MONTEIRO wrote: > > > > Hi, > > > > not sure to understand the question/issue. > > Tomcat is responsible for managing Servlet filters and OpenEJB does not > > skip them. > > > > Hope it helps > > Jean-Louis > > > > I've added the SPNEGO servlet filter on my tomcat instance ( > http://spnego.sourceforge.net/spnego_tomcat.html ), and it seems that any > request to the web service skips the additional filter. Upon debugging > deeply on the tomcat source, I've found that when I try to request pages in > root or other directories it picks-up the thing I added on the filter > chain. > When I try to access any of my webservices it seems to always not pick-up > anything in the filter-chain. > > My filter url is: "/*" > > It is able to capture: > /hello.jsp > /hello.asp > /hello > /openejb/hello.jsp > /openejb/hello.asp > > It doesn't run on the web service call: > /ApplicationWebService > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Tomcat-Servlet-Filters-or-Valves-and-OpenEJB-tp3680204p3680473.html > Sent from the OpenEJB User mailing list archive at Nabble.com. >
