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/18 03:10:44 UTC
[jira] Created: (ODE-393) do not load Rampart in the axis2.xml
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.
[jira] Updated: (ODE-393) do not load Rampart in the axis2.xml
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (ODE-393) do not load Rampart in the axis2.xml
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (ODE-393) do not load Rampart in the axis2.xml
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon closed ODE-393.
----------------------------
Resolution: Fixed
> 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.
[jira] Commented: (ODE-393) do not load Rampart in the axis2.xml
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ 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.