You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2016/01/07 12:13:39 UTC
[jira] [Resolved] (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 ]
Robbie Gemmell resolved PROTON-313.
-----------------------------------
Resolution: Fixed
Assignee: (was: Philip Harvey)
This was fixed at some point long ago, the remotelySettled() method is on the Delivery interface now, so resolving the JIRA.
> [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
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)