You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Saravanakumar Selvaraj (JIRA)" <ji...@apache.org> on 2017/07/16 21:57:00 UTC

[jira] [Updated] (CAMEL-11548) camel-undertow consumer shall use InOut ExchangePattern

     [ https://issues.apache.org/jira/browse/CAMEL-11548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Saravanakumar Selvaraj updated CAMEL-11548:
-------------------------------------------
    Description: 
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

  was:
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}


> 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}
> 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)