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

ASF GitHub Bot commented on CAMEL-10286:
----------------------------------------

GitHub user tivv opened a pull request:

    https://github.com/apache/camel/pull/1154

    CAMEL-10286

    Allow async bean method in bean language with J8 CompletableFuture

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tivv/camel async-default-producer-template

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1154.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1154
    
----
commit df96df0ef4fad58417b98865e7893076e05c4531
Author: Vitalii Tymchyshyn <[email protected]>
Date:   2016-09-04T19:02:47Z

    CAMEL-10286
    Allow async bean method in bean language with J8 CompletableFuture

----


> Allow async bean method in bean language with J8 CompletableFuture
> ------------------------------------------------------------------
>
>                 Key: CAMEL-10286
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10286
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Vitalii Tymchyshyn
>             Fix For: 2.18.0
>
>
> Allow easy creation of asyncrhonous methods called from bean language.
> Proposed solution is to allow such methods to return CompletableFuture.
> Such return would automatically be treated as async invocation.
> Non-null result will be used as resulting body.
> Any async exception will be propagated to proper error handling.
> Note that if CompletableFuture would return null, it won't be used as 
> resulting body. Rather resulting body will not be changed. It would help in 
> use cases when processing method just does some work and returns 
> CompletableFuture<Void>. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to