-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support WebApplicationContext. #7
Conversation
|
||
import java.util.Map; | ||
|
||
public class FilterConfiguration { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need a Configuration object for servlet filters? Can't they just be bean references like all the other dropwizard components?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can use bean references and add through this method addFilter(Filter filter, String urlPattern). In order to get urlPattern, I think, we should have DropwizardFilter interfact that is extended from javax.servle.Filter and provide getUrlPattern method. Then, all Filter bean will implement DropwizardFilter interface. How do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The main reason, I can't use bean references, because DelegatingFilterProxy requires ServletContext to initiate.
Can we update the README.md with documentation concerning what this does and how to use it? |
I updated README.md to reflect the changes |
+1 |
Support WebApplicationContext.
No description provided.