Hi,
On 16/01/14 14:47, helander wrote:
Hi Sergey,
I am not sure what you mean by side-effects,
I thought for a moment it was to do with the security filters having no
effects
but this is what I see (or
really: NOT see) :
I have a web application (WAR) that have a Web Filter and a Camel Servlet.
This filter is used throughout a number of applications and is configured to
be activated by all requests ("/*") to the application . When I make a
request to the Camel Servlet part of the URI context, the request does not
pass thru the filter prior to ending up in the route that is connected
("from servlet://...") the Camel Servlet.
Do the Camel Servlet install any filters in the filter chain? That would be
the only reason I can come up with that would explain why my filter is not
called prior to the Camel Servlet.
May be a servletName parameter should be used
Cheers, Sergey
/Lasse
--
View this message in context:
http://camel.465427.n5.nabble.com/Web-filter-and-camel-servlet-tp5746054p5746064.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
