camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "liugang" <>
Subject RE: [Question] Seems wireTap will always copy the origin Message
Date Fri, 26 Oct 2012 09:19:40 GMT

Thanks for your quick reply, I have fired a bug .

And one more question: 

The maven dependencies of camel-saxon were changed from 2.9.3 to 2.10.2 ,
and on 2.10.0, the dependencies are:


But unfortunately, the net.sf.saxon/saxon9he is a signed jar, so we can't
use the maven-shade-plugin to package it into a shade jar, unless we exclude
all "META-INF/*.RSA", "META-INF/*.DSA" and "META-INF/*.SF".

I'd like to know it will always use the saxon9he infuture? Or the
dependencies will be changed time to time?

skype: gang.liu.talendbj

-----Original Message-----
From: Claus Ibsen [] 
Sent: Friday, October 26, 2012 5:04 PM
Subject: Re: [Question] Seems wireTap will always copy the origin Message

On Fri, Oct 26, 2012 at 10:36 AM, liugang <> wrote:
> Hi All:
> I found the wiretap will always copy the original exchange message after
> deprecated those methods like " wireTap(String uri, boolean copy,
> body) " and " wireTap(String uri, boolean copy, Processor processor)" .
> Checked the source code of org.apache.camel.model.WireTapDefinition<Type>,
> the isCopy() and copy() method are:
>     public WireTapDefinition<Type> copy() {
>         setCopy(true);
>         return this;
>     }
>     public boolean isCopy() {
>         // should default to true if not configured
>         return copy != null ? copy : true;
>     }
> So, no matter, we use '.wireTap("XX")' or '.wireTap("XX").copy()' , it
> always copy the original exchange message.
> Is It a bug?

Ah yeah copy() should accept a boolean so you can control it. Feel
free to log a JIRA.
And a patch is also welcome.

Then @deprecated the copy() method, and add a new copy(boolean)

> Thanks
> GangLiu

Claus Ibsen
Red Hat, Inc.
FuseSource is now part of Red Hat
Twitter: davsclaus
Author of Camel in Action:

View raw message