You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Sukma Verdianto (JIRA)" <ji...@apache.org> on 2008/04/25 12:19:56 UTC
[jira] Created: (ODE-275) Provide a configurable handler to support
WS-RM
Provide a configurable handler to support WS-RM
-----------------------------------------------
Key: ODE-275
URL: https://issues.apache.org/jira/browse/ODE-275
Project: ODE
Issue Type: New Feature
Components: Axis2 Integration
Reporter: Sukma Verdianto
Custom code is required to enable WS-RM modules in Axis2 (to set WS-RM specific options).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-275) Provide a configurable handler to
support WS-RM
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594282#action_12594282 ]
Alexis Midon commented on ODE-275:
----------------------------------
Sukma,
For each service, you can place a [serviceLocalName].axis2 file at the root of the process bundle. Currently, this file can only be added on the server, under var/processes/[PROCESS]. The file is polled for update every 30 seconds.
So configuration for external endpoint is available.
Hope it helps.
Alexis
> Provide a configurable handler to support WS-RM
> -----------------------------------------------
>
> Key: ODE-275
> URL: https://issues.apache.org/jira/browse/ODE-275
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Reporter: Sukma Verdianto
>
> Custom code is required to enable Axis2 WS-RM modules (to set WS-RM specific options) at caller side.
> Sandesha2 requires these following steps to be done before sending the messages :
> 1. Engage sandesha2 and addressing modules, could be done by loading axis2 configuration per external endpoint which also define RMPhase.
> 2. Set SandeshaClientConstants.LAST_MESSAGE property to true, could be done by adding a custom handler that will be called before invocation.
> This require changes to ExternalService.
> A sandesha userguide that show the example of writing simple WS-RM client is http://ws.apache.org/sandesha/sandesha2/userGuide.html#writing_clients
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-275) Provide a configurable handler to
support WS-RM
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12602339#action_12602339 ]
Alexis Midon commented on ODE-275:
----------------------------------
Here is proposal for an implementation (and the consequent patch).
A new interface org.apache.ode.axis2.ServiceClientHandler exposes a method:
handle(QName serviceName, String portName, ServiceClient client) throws AxisFault.
An implementation of this interface may be specified with the property "axis2.service.client.handler" in the integration-layer.properties (see ODE-295).
Each SoapExternalService has one handler instance per thread (same pattern as for ServiceClient and Options).
This instance is invoked each time the ServiceClient is created. This might happen on the first call, or if the handler implementation or the Axis2 Options have changed (The value of this property is checked every 30 seconds).
The handler is invoked after the loading of the xml file [serviceLocalName].axis2
Here the order of precedence of the 3 ServiceClient configuration steps available: (least important first)
#1. loading of [serviceLocalName].axis2
#2. Options set in integration-layer.properties
#2. ServiceHandler
Feedback welcome.
> Provide a configurable handler to support WS-RM
> -----------------------------------------------
>
> Key: ODE-275
> URL: https://issues.apache.org/jira/browse/ODE-275
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Reporter: Sukma Verdianto
> Fix For: 1.3
>
>
> Custom code is required to enable Axis2 WS-RM modules (to set WS-RM specific options) at caller side.
> Sandesha2 requires these following steps to be done before sending the messages :
> 1. Engage sandesha2 and addressing modules, could be done by loading axis2 configuration per external endpoint which also define RMPhase.
> 2. Set SandeshaClientConstants.LAST_MESSAGE property to true, could be done by adding a custom handler that will be called before invocation.
> This require changes to ExternalService.
> A sandesha userguide that show the example of writing simple WS-RM client is http://ws.apache.org/sandesha/sandesha2/userGuide.html#writing_clients
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-275) Provide a configurable handler to
support WS-RM
Posted by "Sukma Verdianto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594514#action_12594514 ]
Sukma Verdianto commented on ODE-275:
-------------------------------------
Thanks Alexis,
That should solve the #1 step to achieve the goal.
I think we need step 2 to be added to SoapExternalService, eg, by passing ServiceClient or OperationClient to registered handler.
The handler will then set various options (SandeshaClientConstants.LAST_MESSAGE, Sandesha report), so we can have WS-RM enable on service client side. Please corrent me if I am wrong.
This probably also useful for other Axis2 modules - eg, Security
Any idea?
Regards,
Sukma
> Provide a configurable handler to support WS-RM
> -----------------------------------------------
>
> Key: ODE-275
> URL: https://issues.apache.org/jira/browse/ODE-275
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Reporter: Sukma Verdianto
>
> Custom code is required to enable Axis2 WS-RM modules (to set WS-RM specific options) at caller side.
> Sandesha2 requires these following steps to be done before sending the messages :
> 1. Engage sandesha2 and addressing modules, could be done by loading axis2 configuration per external endpoint which also define RMPhase.
> 2. Set SandeshaClientConstants.LAST_MESSAGE property to true, could be done by adding a custom handler that will be called before invocation.
> This require changes to ExternalService.
> A sandesha userguide that show the example of writing simple WS-RM client is http://ws.apache.org/sandesha/sandesha2/userGuide.html#writing_clients
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-275) Provide a configurable handler to support
WS-RM
Posted by "Sukma Verdianto (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sukma Verdianto updated ODE-275:
--------------------------------
Description:
Custom code is required to enable Axis2 WS-RM modules (to set WS-RM specific options) at caller side.
Sandesha2 requires these following steps to be done before sending the messages :
1. Engage sandesha2 and addressing modules, could be done by loading axis2 configuration per external endpoint which also define RMPhase.
2. Set SandeshaClientConstants.LAST_MESSAGE property to true, could be done by adding a custom handler that will be called before invocation.
This require changes to ExternalService.
A sandesha userguide that show the example of writing simple WS-RM client is http://ws.apache.org/sandesha/sandesha2/userGuide.html#writing_clients
was:Custom code is required to enable WS-RM modules in Axis2 (to set WS-RM specific options).
> Provide a configurable handler to support WS-RM
> -----------------------------------------------
>
> Key: ODE-275
> URL: https://issues.apache.org/jira/browse/ODE-275
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Reporter: Sukma Verdianto
>
> Custom code is required to enable Axis2 WS-RM modules (to set WS-RM specific options) at caller side.
> Sandesha2 requires these following steps to be done before sending the messages :
> 1. Engage sandesha2 and addressing modules, could be done by loading axis2 configuration per external endpoint which also define RMPhase.
> 2. Set SandeshaClientConstants.LAST_MESSAGE property to true, could be done by adding a custom handler that will be called before invocation.
> This require changes to ExternalService.
> A sandesha userguide that show the example of writing simple WS-RM client is http://ws.apache.org/sandesha/sandesha2/userGuide.html#writing_clients
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-275) Provide a configurable handler to support
WS-RM
Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexis Midon updated ODE-275:
-----------------------------
Attachment: ODE-275-branch.patch#1.txt
> Provide a configurable handler to support WS-RM
> -----------------------------------------------
>
> Key: ODE-275
> URL: https://issues.apache.org/jira/browse/ODE-275
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Reporter: Sukma Verdianto
> Fix For: 1.3
>
> Attachments: ODE-275-branch.patch#1.txt
>
>
> Custom code is required to enable Axis2 WS-RM modules (to set WS-RM specific options) at caller side.
> Sandesha2 requires these following steps to be done before sending the messages :
> 1. Engage sandesha2 and addressing modules, could be done by loading axis2 configuration per external endpoint which also define RMPhase.
> 2. Set SandeshaClientConstants.LAST_MESSAGE property to true, could be done by adding a custom handler that will be called before invocation.
> This require changes to ExternalService.
> A sandesha userguide that show the example of writing simple WS-RM client is http://ws.apache.org/sandesha/sandesha2/userGuide.html#writing_clients
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-275) Provide a configurable handler to support
WS-RM
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou updated ODE-275:
------------------------------
Fix Version/s: (was: 1.3)
2.0
> Provide a configurable handler to support WS-RM
> -----------------------------------------------
>
> Key: ODE-275
> URL: https://issues.apache.org/jira/browse/ODE-275
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Reporter: Sukma Verdianto
> Fix For: 2.0
>
> Attachments: ODE-275-branch.patch#1.txt
>
>
> Custom code is required to enable Axis2 WS-RM modules (to set WS-RM specific options) at caller side.
> Sandesha2 requires these following steps to be done before sending the messages :
> 1. Engage sandesha2 and addressing modules, could be done by loading axis2 configuration per external endpoint which also define RMPhase.
> 2. Set SandeshaClientConstants.LAST_MESSAGE property to true, could be done by adding a custom handler that will be called before invocation.
> This require changes to ExternalService.
> A sandesha userguide that show the example of writing simple WS-RM client is http://ws.apache.org/sandesha/sandesha2/userGuide.html#writing_clients
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-275) Provide a configurable handler to support
WS-RM
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou updated ODE-275:
------------------------------
Fix Version/s: 1.3
> Provide a configurable handler to support WS-RM
> -----------------------------------------------
>
> Key: ODE-275
> URL: https://issues.apache.org/jira/browse/ODE-275
> Project: ODE
> Issue Type: New Feature
> Components: Axis2 Integration
> Reporter: Sukma Verdianto
> Fix For: 1.3
>
>
> Custom code is required to enable Axis2 WS-RM modules (to set WS-RM specific options) at caller side.
> Sandesha2 requires these following steps to be done before sending the messages :
> 1. Engage sandesha2 and addressing modules, could be done by loading axis2 configuration per external endpoint which also define RMPhase.
> 2. Set SandeshaClientConstants.LAST_MESSAGE property to true, could be done by adding a custom handler that will be called before invocation.
> This require changes to ExternalService.
> A sandesha userguide that show the example of writing simple WS-RM client is http://ws.apache.org/sandesha/sandesha2/userGuide.html#writing_clients
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.