You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Rafael H. Schloming (JIRA)" <ji...@apache.org> on 2013/09/03 17:03:04 UTC
[jira] [Updated] (PROTON-313) [Proton-J] no consistent way to
determine remote settlement
[ https://issues.apache.org/jira/browse/PROTON-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafael H. Schloming updated PROTON-313:
---------------------------------------
Fix Version/s: (was: 0.5)
> [Proton-J] no consistent way to determine remote settlement
> -----------------------------------------------------------
>
> Key: PROTON-313
> URL: https://issues.apache.org/jira/browse/PROTON-313
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.4
> Reporter: Robbie Gemmell
> Assignee: Philip Harvey
>
> In order to determine remote settlement it is currently necessary to perform a cast :
> {noformat}
> // TODO - remove this hack when Proton-J and -C APIs are properly aligned
> // The C API defines isSettled as being true if the delivery has been settled locally OR remotely
> return _delivery.isSettled() || ((_delivery instanceof DeliveryImpl && ((DeliveryImpl)_delivery).remotelySettled()));
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira