Got it , thanks. GangLiu Skype: gang.liu.talendbj
-----Original Message----- From: Claus Ibsen [mailto:claus.ib...@gmail.com] Sent: Monday, October 29, 2012 4:49 PM To: users@camel.apache.org Subject: Re: [Question] Seems wireTap will always copy the origin Message On Fri, Oct 26, 2012 at 11:19 AM, liugang <clevers...@gmail.com> wrote: > Hi: > > Thanks for your quick reply, I have fired a bug > https://issues.apache.org/jira/browse/CAMEL-5746 . > > 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: > > <dependency> > <groupId>net.sf.saxon</groupId> > <artifactId>saxon9he</artifactId> > </dependency> > > 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? > Camel will upgrade to never releases os Saxon when they are released and in Maven Central. > Thanks > GangLiu > msn: liugang_0...@hotmail.com > skype: gang.liu.talendbj > > -----Original Message----- > From: Claus Ibsen [mailto:claus.ib...@gmail.com] > Sent: Friday, October 26, 2012 5:04 PM > To: users@camel.apache.org > Subject: Re: [Question] Seems wireTap will always copy the origin Message > > On Fri, Oct 26, 2012 at 10:36 AM, liugang <clevers...@gmail.com> wrote: >> Hi All: >> >> I found the wiretap will always copy the original exchange message after >> deprecated those methods like " wireTap(String uri, boolean copy, > Expression >> 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 > will >> 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 > Email: cib...@redhat.com > Web: http://fusesource.com > Twitter: davsclaus > Blog: http://davsclaus.com > Author of Camel in Action: http://www.manning.com/ibsen > -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
