[
https://issues.apache.org/jira/browse/SANDESHA2-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chamikara Jayalath resolved SANDESHA2-78.
-----------------------------------------
Resolution: Fixed
Assignee: Chamikara Jayalath
> Failure to send LastMessage before Terminating if not already sent
> ------------------------------------------------------------------
>
> Key: SANDESHA2-78
> URL: https://issues.apache.org/jira/browse/SANDESHA2-78
> Project: Sandesha2
> Issue Type: Bug
> Environment: RM 1.0
> Reporter: Paul Fremantle
> Assigned To: Chamikara Jayalath
>
> If the user terminates a sequence using
> SandeshaClient.terminateSequence(stub._getServiceClient());
> but has not explicitly tagged a message LastMessage, then we must send an
> empty LastMessage before sending the TS. Currently we just send
> TerminateSequence which is a protocol violation.
> If you try this with .NET you get this response:
> <s:Text xml:lang="en-GB">The wsrm:TerminateSequence protocol
> message was transmitted before the sequence was successfully
> completed.</s:Text>
> In the RM 1.0 spec it states:
> A RM Source endpoint MUST include a <LastMessage> element in the <Sequence>
> element for the last message in a Sequence.
> The empty LastMessage is there to allow this to happen in this case.
--
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]
