[
https://issues.apache.org/jira/browse/KNOX-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783442#comment-13783442
]
Dilli Arumugam commented on KNOX-176:
-------------------------------------
It would help, is there is some sort of specification that describes current
deployment flow, starting from topology file, what are the steps in the
process of mapping it to a war. What are the possible customization points?
Can someone get rid of of one provider in the topology file and expect gateway
to work? What should one do to add a a new provider? Configuration file
changes, new code to be written. Is it as simple as adding a java class in the
class path? etc.
> Per Service overrides of Provider parameters
> --------------------------------------------
>
> Key: KNOX-176
> URL: https://issues.apache.org/jira/browse/KNOX-176
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Affects Versions: 0.3.0
> Reporter: Kevin Minder
> Fix For: 0.4.0
>
>
> Within the topology file it should be possible to override some of the
> provider params at the service level. The complicating factor is figuring
> how what filters should be setup with the service's params. Should the param
> names be prefixed with a provider's role and name?
> <topology>
> <gateway>
> <provider>
> <role>X</role?
> <param><name>Y</name><value>Z</value></param>
> </provider>
> </gateway>
> <service>
> <role>A</role>
> <param><name>Y</name><value>Z</value></param>
> </service>
> </topology>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
