[
https://issues.apache.org/jira/browse/ODE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641208#action_12641208
]
Alexis Midon commented on ODE-393:
----------------------------------
fixed in r706455
Using the name/targetNamespace attributes in service.xml does not help.
Actually the list of modules is updated properly but the modules are not
engaged.
So the fix consists in engaging the module mentioned in service.xml
programmatically.
> do not load Rampart in the axis2.xml
> ------------------------------------
>
> Key: ODE-393
> URL: https://issues.apache.org/jira/browse/ODE-393
> Project: ODE
> Issue Type: Improvement
> Components: Axis2 Integration
> Reporter: Alexis Midon
> Assignee: Alexis Midon
> Fix For: 1.3
>
>
> I didn't manage to engage Rampart from a service.xml file like the one below.
> To workaround this issue, Rampart is engaged in the main xis2.xml file. Which
> means Rampart is engaged for *all* services (hosted + invoked).
> I've started a thread on the issue in the axis2 mailing list. One is to set
> the name attribute in <service>. Will try.
> <service>
> <module ref="rampart" />
>
> <parameter name="OutflowSecurity">
> <action>
> ...
> </action>
> </parameter>
> </service>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
