[
https://issues.apache.org/jira/browse/KNOX-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Minder updated KNOX-177:
------------------------------
Description:
Currently it is too complicated to develop a service deployment contributor.
This is caused primarily by the need for each service deployment contributor to
hard code the filters and their order. There should probably be something a
default filter chain template that could be configured by the service
deployment contributor. Then additional service specific filters could be
added to the end of the default chain.
{newcode}
class X {}
{newcode}
was:Currently it is too complicated to develop a service deployment
contributor. This is caused primarily by the need for each service deployment
contributor to hard code the filters and their order. There should probably be
something a default filter chain template that could be configured by the
service deployment contributor. Then additional service specific filters could
be added to the end of the default chain.
> Simplify service deployment contributor implementation
> ------------------------------------------------------
>
> Key: KNOX-177
> URL: https://issues.apache.org/jira/browse/KNOX-177
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.2.0
> Reporter: Kevin Minder
> Fix For: 0.4.0
>
>
> Currently it is too complicated to develop a service deployment contributor.
> This is caused primarily by the need for each service deployment contributor
> to hard code the filters and their order. There should probably be something
> a default filter chain template that could be configured by the service
> deployment contributor. Then additional service specific filters could be
> added to the end of the default chain.
> {newcode}
> class X {}
> {newcode}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
