Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <1990303844.1236595539985.JavaMail.jira@brutus>
Date: Mon, 9 Mar 2009 03:45:39 -0700 (PDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (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
In-Reply-To: <676048452.1235475539388.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Claus Ibsen resolved CAMEL-1376.
--------------------------------

    Resolution: Fixed

Committed revision 751648.

> 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.