You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by "Thomas McKiernan (JIRA)" <ji...@apache.org> on 2006/11/29 11:16:23 UTC
[jira] Updated: (SANDESHA2-53) Allow ServiceClient to specify the
exact internal sequence ID when closing/terminating a sequence.
[ http://issues.apache.org/jira/browse/SANDESHA2-53?page=all ]
Thomas McKiernan updated SANDESHA2-53:
--------------------------------------
Attachment: closeTerminateChanges2.patch
This addresses the issues.
> Allow ServiceClient to specify the exact internal sequence ID when closing/terminating a sequence.
> --------------------------------------------------------------------------------------------------
>
> Key: SANDESHA2-53
> URL: http://issues.apache.org/jira/browse/SANDESHA2-53
> Project: Apache Sandesha2
> Issue Type: Bug
> Reporter: Thomas McKiernan
> Attachments: closeTerminateChanges2.patch
>
>
> We have a requirement to set the internal sequence ID for a service client to use when terminating a sequence.
> I have added a test to check the terminate and close APIs work.
> I've also added the abbility to extract the sequence key from a client side internal sequence ID.
> Finally, it would be good for a closed sequence to not allow any subsequent messages to be sent.
> I will attach a patch later on.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org