[jira] Resolved: (SANDESHA2-74) "Replay" synchronous model not working properly

["Chamikara Jayalath (JIRA)" <ji...@apache.org>]

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

Chamikara Jayalath resolved SANDESHA2-74.
-----------------------------------------

    Resolution: Fixed
      Assignee: Chamikara Jayalath

TerminateSequence actionMapping was moved to the InOnlyOperation.

> "Replay" synchronous model not working properly 
> ------------------------------------------------
>
>                 Key: SANDESHA2-74
>                 URL: https://issues.apache.org/jira/browse/SANDESHA2-74
>             Project: Sandesha2
>          Issue Type: Bug
>         Environment: Axis2 talking to .NET
>            Reporter: Paul Fremantle
>         Assigned To: Chamikara Jayalath
>
> This is fairly complex :-)
> I have an Axis2 client talking to .NET WCF. I'm using a synchronous call with two-way RM and its marked as LastMessage.
> After the operation goes through, the TS flows from Client to Server correctly. On the HTTP response, .NET flows back a TS. This has a wsa:Action but no wsa:MessageID. 
> In Axis2 the TS method is marked as InOut as a "hack". Its used on the server side to pass back the corresponding server-side TS. However, this means that at the client side the WSA validation is expecting a wsa:MessageID on the incoming TS. (wsa:MessageID is required on the in of any in-out). 
> Therefore the hack is causing an exception.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org