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 Mon, 17 Jul 2017 10:05:01 GMT

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

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

Github user saravanakumar1987 closed the pull request at:

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


> 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
>            Assignee: Zoran Regvart
>            Priority: Minor
>             Fix For: 2.20.0
>
>
> 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}
> So it also becomes impossible to change to undertow from netty4-http,restlet or camel-jetty
while using Rest DSL



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

Mime
View raw message