You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2019/01/02 08:18:00 UTC

[jira] [Commented] (CAMEL-11361) AsyncCallback API - Include Exchange if we do change the API

    [ https://issues.apache.org/jira/browse/CAMEL-11361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731825#comment-16731825 ] 

Claus Ibsen commented on CAMEL-11361:
-------------------------------------

Oh please hold on this one as its a bigger API change and we would need to consider if its worth the "pain".

> AsyncCallback API - Include Exchange if we do change the API
> ------------------------------------------------------------
>
>                 Key: CAMEL-11361
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11361
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Ramu
>            Priority: Major
>             Fix For: 3.0.0, Future
>
>
> The AsyncCallback has a done method with only a boolean. If we had included the Exchange as well, then we could often obtain any needed information in the callback method from the exchange instead of having to refer to instances from the surrounding scope via final keywords.
> This also avoids creating a new object per call which, which then take up memory. 
>     void done(boolean syncDone, Exchange exchange)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)