Yeah, you need to use the block to avoid this issue.
-- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem On Thursday, June 27, 2013 at 3:15 PM, liugang594 Liu wrote: > I found a way to make it works: change wireTap("direct:a").id("wireTapId") > to wireTap("direct:a").id("wireTapId").end() , then it works. > > > 2013/6/27 liugang594 Liu <clevers...@gmail.com (mailto:clevers...@gmail.com)> > > > Hi All: > > > > I have below route: > > > > from("timer:foo").routeId("route1").setBody(constant("Hello")).id("setBodyID").wireTap("direct:a").id("wireTapId").process(new > > Processor(){...}).id("processId"); > > > > When I'm trying to trace each node by id, I found the id of wireTap will > > be always "processId". Seems all sub-classes of ProcessorDefinition have > > the same problem. > > > > is it a bug of Camel? or is there any other way to resolve this problem? > > > > -- > > Thanks > > GangLiu > > MSN: liugang_0...@hotmail.com (mailto:liugang_0...@hotmail.com) > > Skype: gang.liu.talendbj > > > > > -- > Thanks > GangLiu > MSN: liugang_0...@hotmail.com (mailto:liugang_0...@hotmail.com) > Skype: gang.liu.talendbj
