[jira] Commented: (TUSCANY-3592) binding-ws-runtime-axis2 does not handle Web services bidirectional service invocations correctly

["Mike Edwards (JIRA)" <de...@tuscany.apache.org>]

    [ https://issues.apache.org/jira/browse/TUSCANY-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880327#action_12880327 ] 

Mike Edwards commented on TUSCANY-3592:
---------------------------------------

Sub-task 5:

Where a bidirectional service is invoked, it will arrive with an EPR for the callback, either in a wsa:From header or in a wsa:ReplyTo header.  The wsa:Address contained in the header can be accompanied by wsa:ReferenceProperties, as follows:


   <wsa:From>
     <wsa:Address>http://example.com/callback</wsa:Address>
     <wsa:ReferenceProperties>
       <myNS:SomeID>1</myNS:SomeID>
     </wsa:ReferenceProperties>
   </wsa:From>

When the ReferenceProperties are present, they MUST be transferred to any callback invocation and accompany the wsa:To header:

   <wsa:To>http://example.com/callback</wsa:To>
   <myNS:SomeID>1</myNS:SomeID>


> binding-ws-runtime-axis2 does not handle Web services bidirectional service invocations correctly
> -------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3592
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3592
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Axis Binding Extension
>    Affects Versions: Java-SCA-2.0-M4
>            Reporter: Mike Edwards
>            Assignee: Mike Edwards
>             Fix For: Java-SCA-2.0
>
>
> binding-ws-runtime-axis2 has problems handling Web services bidirectional service invocations.
> These problems are revealed in the OASIS binding.ws test suite, in particular the testcases BWS_5001 to BWS_5006 inclusive, where the "other side" of the service interaction is a pure JAXWS application providing both client and service endpoints.
> There are a number of problems, as follows:
> 1) Callback EPR is not correctly transferred from the bidirectional service invocation to the callback reference so that the callback fails
> 2) The OASIS Web services spec requires that a series of specific SOAP headers are handled, both on receipt of a service invocation and on callback.  The current Tuscany code does not handle these correctly:
> wsa:To
> wsa:Action
> wsa:MessageID
> wsa:RelatesTo
> wsa:ReferenceParameters
> - this needs to be done both when Tuscany hosts a bidirectional service and makes callbacks and also when Tuscany invokes a bidirectional service and hosts a callback service.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.