You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alexis Midon (JIRA)" <ji...@apache.org> on 2008/10/21 01:30:44 UTC

[jira] Updated: (ODE-393) do not load Rampart in the axis2.xml

     [ https://issues.apache.org/jira/browse/ODE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexis Midon updated ODE-393:
-----------------------------

    Comment: was deleted

> 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.