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:37:26 UTC
[jira] [Comment Edited] (KNOX-177) Simplify service deployment
contributor implementation
[ https://issues.apache.org/jira/browse/KNOX-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13809076#comment-13809076 ]
Kevin Minder edited comment on KNOX-177 at 10/30/13 1:36 PM:
-------------------------------------------------------------
Design notes in the wiki:
https://cwiki.apache.org/confluence/display/KNOX/Simplify+service+deployment+contributor+implementation+%28KNOX-177%29
was (Author: kminder):
Design notes in the wiki:
https://cwiki.apache.org/confluence/display/KNOX/Simplify+service+deployment+contributor+implementation+(KNOX-177)
> 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)