camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen">
Subject RE: route definition: component response routing
Date Tue, 08 Jul 2008 10:57:23 GMT

Vladim could you give an example? I read your question a bit differently than Charles.

If you mean what Camel does if you have a route like this?


And you send an exchange to "xxx". Then Camel will process the exchange and return a response
to the client.

Eg: as this unit test demonstrates:

    public void testNoToType() throws Exception {
        Object response = template.requestBody("direct:in", "Hello");
        assertEquals("Hello World", response);

    protected RouteBuilder createRouteBuilder() throws Exception {
        return new RouteBuilder() {
            public void configure() throws Exception {
                from("direct:in").process(new Processor() {
                    public void process(Exchange exchange) throws Exception {
                        String body = exchange.getIn().getBody(String.class);
                        exchange.getOut(true).setBody(body + " World");

Med venlig hilsen
Claus Ibsen
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576

-----Original Message-----
From: cmoulliard [] 
Sent: 8. juli 2008 09:05
Subject: Re: route definition: component response routing

Hi Vlad,

If the destination endpoint is not defined, an error will be generated when
your message will be send. Different strategies exist to avoid to lost your
message in this situation :

- Implement a DeadLetterchannel,
- Define your "from" endpoint as a transactional endpoint to provide a



volenin wrote:
> Does anyone have any suggestion re: this question?...
> On Sun, Jun 29, 2008 at 5:47 PM, Vlad Olenin <> wrote:
>> Hi,
>> I was browsing through the documentation recently trying to find the
>> answer
>> for the following question. If the outbound route from one of the
>> endpoints
>> is not defined, does it mean that the response that component is creating
>> would be propagated back through the request chain? Or it would just
>> terminate on that endpoint? In other words, does Camel behavior in this
>> case
>> resembles that of Mule or not? (From what I read, in Mule if the outbound
>> route is not defined, the message would 'bounce back' along the
>> invocation
>> chain towards the original caller).
>> Thanks,
>> Vlad

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message