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