[
https://issues.apache.org/jira/browse/SANDESHA2-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hans G Knudsen updated SANDESHA2-116:
-------------------------------------
Attachment: sync_last_message.txt
Patch for SaneshaClient.terminateSequence - which sets up OUT_IN MEP for
LastMessage when rm is protocol-syncronous (the Microsoft RM 1.0 way).
With the patch the
LastMessage is transmitted and Sandesha replays - until a LastMessage(Response)
is received with server acknowledge...
Also the
SandeshaClient.waitUntilSequenceCompleted (serviceClient);
waits until ack.
Tested for positive test on both http and mail transport.
Tested with a client RM timeout before service responds.
> Terminate Sequence over mailtransport does not setup SynchronousMailListener
> ----------------------------------------------------------------------------
>
> Key: SANDESHA2-116
> URL: https://issues.apache.org/jira/browse/SANDESHA2-116
> Project: Sandesha2
> Issue Type: Bug
> Environment: Axis2/Sandesha2 pre/rc branch_1_3. WSRM 1.0
> Reporter: Hans G Knudsen
> Priority: Blocker
> Attachments: sync_last_message.txt
>
>
> When running sync(replyto=anonymous) over mailtransport sending
> TerminateSequence does not setup SynchronousMailListener - and TS response is
> not handled correctly.
>
> The same should also apply for Acks/LastMessage...
> In util.SpecSpecificConstants.getWSRMOperation - the AxisOperation which
> Axis.transport.mail.EMailSender looks at to determine sync/non-sync is set to
> RM_OUT_ONLY_OPERATION resulting in non-sync.
> I donot know the consequences of changing this to OUT_IN
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
