Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have two filter classes extending from org.springframework.web.filter.RequestContextFilter, both configured in the web.xml in the same way, both using @Component annotation. When I had only one, everything worked correctly. When I added the second one, it didn’t get registered.
Why? How can I solve this? I need the two filters?
Since Spring
@Componentis class based and not name based, the second filter doesn’t load because it’s being shadowed by the first one. The fact that the two implementation classes are different is irrelevant because Spring searches for something extending Filter.The solution is to use a qualifier for each
@Component(e.g.@Component(value = "MyFilter1")) and to declare in theweb.xmlthe name of the filter as the qualifier (e.g.<filter><filter-name>MyFilter</filter-name>...</filter>.Don’t forget to use
org.springframework.web.filter.DelegatingFilterProxyand declare the filter mapping as well.Yes – it’s strange, but I’m answering my own question immediately. I started writing it after searching for a few hours and then had an idea. I tested it and it works – but there’s no reason for someone else to search for a few hours again.