camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11548) camel-undertow consumer shall use InOut ExchangePattern
Date Sun, 16 Jul 2017 21:54:01 GMT

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

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

GitHub user saravanakumar1987 opened a pull request:

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

    CAMEL-11548: Making camel-undertow consumer InOut

    I am not really sure if it is intentional that camel-undertow consumer is InOnly. But
its the odd one among camel-jetty, camel-restlet and netty4-http. 
    
    Please review the PR for : https://issues.apache.org/jira/browse/CAMEL-11548
    
    Thanks,
    Saravanakumar

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

    $ git pull https://github.com/saravanakumar1987/camel master

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

    https://github.com/apache/camel/pull/1829.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 #1829
    
----
commit 6c1c3a53eaf3525ee53d4ef272810003ca09e653
Author: Saravanakumar Selvaraj <saravanakumar.java@gmail.com>
Date:   2017-07-16T21:47:22Z

    CAMEL-11548: Making camel-undertow consumer InOut

----


> camel-undertow consumer shall use InOut ExchangePattern
> -------------------------------------------------------
>
>                 Key: CAMEL-11548
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11548
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-undertow
>    Affects Versions: 2.19.1
>            Reporter: Saravanakumar Selvaraj
>            Priority: Minor
>
> Camel-undertow is the odd one among camel-jetty, camel-restlet and netty4-http. It's
consumer does not use InOut ExchangePattern and hence Request Reply EIP is not possible on
asynchronous endpoints.
> For example, below consumer returns "No response available" instead of "Camel rocks!!"
> {code}
> from("undertow:http://localhost:8081/api").to("seda:foo");
> from("seda:foo").process(exchange -> {
> 	exchange.getIn().setBody("Camel rocks!!");
> });
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message