[
https://issues.apache.org/jira/browse/KNOX-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13832796#comment-13832796
]
ASF subversion and git services commented on KNOX-179:
------------------------------------------------------
Commit ef3ec3546e3dedcc2b8c399fa386dd38b161d83b in branch refs/heads/master
from [~kevin.minder]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-knox.git;h=ef3ec35 ]
KNOX-179: Simple way to introduce new provider/servlet filters into the chains
> Simple way to introduce new provider/servlet filters into the chains
> --------------------------------------------------------------------
>
> Key: KNOX-179
> URL: https://issues.apache.org/jira/browse/KNOX-179
> Project: Apache Knox
> Issue Type: New Feature
> Components: Server
> Affects Versions: 0.3.0
> Reporter: Kevin Minder
> Assignee: Kevin Minder
> Fix For: 0.4.0
>
> Attachments:
> KNOX-179__Simple_way_to_introduce_new_provider_servlet_filters_into_the_chain_.patch
>
>
> There needs to be an easier way to introduce new filters into the chain.
> I've been thinking that we can provide two "out-of-the-box" providers (e.g.
> pre-chain-filter and pre-dispatch-filter or initial-filter and final-filter,
> etc.). If enabled they would contribute a filter using one of the params as
> the class name. All other params would be used as filter init params. All
> current service contributors would need to be changed to always include these
> filters in the chain.
> Design proposal:
> https://cwiki.apache.org/confluence/display/KNOX/Simple+way+to+introduce+new+Provider+(KNOX-179)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
