[jira] [Commented] (KNOX-179) Simple way to introduce new provider/servlet filters into the chains

["Kevin Minder (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KNOX-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809075#comment-13809075 ] 

Kevin Minder commented on KNOX-179:
-----------------------------------

Another alternative is to provide a built-in default Provider that uses config params to control its behavior.  If coupled with a mechanism to externalize the provider/filter-chain definition this would allow a provider to be setup without code.  One of the params would of course need to be the name of the filter class that it would contribute to any chain.

> 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
>             Fix For: 0.4.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.1#6144)