You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Minder (JIRA)" <ji...@apache.org> on 2013/10/30 14:33:25 UTC

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

     [ https://issues.apache.org/jira/browse/KNOX-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Minder updated KNOX-179:
------------------------------

    Summary: Simple way to introduce new provider/servlet filters into the chains  (was: Simple way to introduce new 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
>             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)