[
https://issues.apache.org/jira/browse/ODE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640726#action_12640726
]
Alexis Midon commented on ODE-393:
----------------------------------
actually it works fine when the service name is set.
<service name="sample03"
targetNamespace="http://sample03.samples.rampart.apache.org";>
<module ref="rampart" />
</service>
> 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.
