camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-1376) wiretap() to be able to send an InOnly message exchange with the result of an InOut request without affecting the current message exchange
Date Mon, 09 Mar 2009 10:45:39 GMT

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

Claus Ibsen updated CAMEL-1376:
-------------------------------

    Component/s: camel-core

> wiretap() to be able to send an InOnly message exchange with the result of an InOut request
without affecting the current message exchange
> ------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1376
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1376
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: James Strachan
>            Assignee: Claus Ibsen
>             Fix For: 2.0.0
>
>
> we should be able to do something like this...
> {code}
> from("jetty:http://localhost:8585/cxf/HelloWorld")
>   .to("http://localhost:8080/cxf/HelloWorld")
>    .wiretap("seda:cheese");
> {code}
> such that the *seda:cheese* gets the output of the HelloWorld service as an InOut - but
the response is returned fine to the HTTP client. i.e. the presence of the wiretap() does
not in any way affect the exchange - it appears to work exactly the same as
> {code}
> from("jetty:http://localhost:8585/cxf/HelloWorld")
>   .to("http://localhost:8080/cxf/HelloWorld");
> {code}
> and any output of the seda:cheese does not affect the response to the HTTP client.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message