I merged the patch into camel-2.13.x and camel-2.12.x at the mean time :) You can try to use camel-2.13.3-SNAPSHOT, camel-2.12.5-SNAPSHOT if you like.
-- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On July 3, 2014 at 5:10:13 PM, Jörn Gersdorf ([email protected]) wrote: > You're really fast :-) I guess this will be for the moment just in > 2.14-SNAPSHOT? > > Viele Grüße > Jörn > > > On Thu, Jul 3, 2014 at 10:10 AM, Willem Jiang > wrote: > > > I already committed a quick fix[1] for it :) > > > > [1]http://git-wip-us.apache.org/repos/asf/camel/commit/53fe8451 > > > > > > -- > > Willem Jiang > > > > Red Hat, Inc. > > Web: http://www.redhat.com > > Blog: http://willemjiang.blogspot.com (English) > > http://jnn.iteye.com (Chinese) > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > > > > > On July 3, 2014 at 3:33:30 PM, Jörn Gersdorf ([email protected]) wrote: > > > Thanks, Willem. I attached a unit test for this issue. > > > > > > Kind regards, > > > Jörn > > > > > > Viele Grüße > > > Jörn > > > > > > > > > On Thu, Jul 3, 2014 at 5:17 AM, Willem Jiang wrote: > > > > > > > FYI, I just created JIRA[1] for it. > > > > > > > > [1]https://issues.apache.org/jira/browse/CAMEL-7570 > > > > > > > > -- > > > > Willem Jiang > > > > > > > > Red Hat, Inc. > > > > Web: http://www.redhat.com > > > > Blog: http://willemjiang.blogspot.com (English) > > > > http://jnn.iteye.com (Chinese) > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > > > > > > > > > On July 3, 2014 at 12:20:19 AM, Claus Ibsen ([email protected]) > > wrote: > > > > > Hi > > > > > > > > > > Yeah this can be improved, fell free to log a JIRA ticket about this > > > > > http://camel.apache.org/support.html > > > > > > > > > > On Wed, Jul 2, 2014 at 5:46 PM, Jörn Gersdorf wrote: > > > > > > Hi, > > > > > > > > > > > > I'm playing with Camel 2.12 and the event notification system and > > > > > > discovered a difference in behavior using enrich() as opposed to > > > > > > inOnly()/inOut() wrt events sent out. > > > > > > > > > > > > When using inOnly() or inOut() in the example below I see an > > > > > > ExchangeSendingEvent and an ExchangeSentEvent when > > sending/receiving > > > > to the > > > > > > activemq endpoint. > > > > > > > > > > > > However, and this is confusing, when using enrich() neither > > > > > > ExchangeSendingEvent nor ExchangeSentEvent is produced. > > > > > > > > > > > > Is this by purpose or a bug? > > > > > > > > > > > > Kind regards, > > > > > > Jörn > > > > > > > > > > > > Example route: > > > > > > > > > > > > from("direct:start") > > > > > > .enrich("activemq:enricher") > > > > > > // .inOnly("activemq:enricher") > > > > > > // .inOut("activemq:enricher") > > > > > > .to("mock:end"); > > > > > > > > > > > > from("activemq:enricher") > > > > > > .setBody(simple("Hello, ${body}!")); > > > > > > > > > > > > > > > > > > > > -- > > > > > Claus Ibsen > > > > > ----------------- > > > > > Red Hat, Inc. > > > > > Email: [email protected] > > > > > Twitter: davsclaus > > > > > Blog: http://davsclaus.com > > > > > Author of Camel in Action: http://www.manning.com/ibsen > > > > > hawtio: http://hawt.io/ > > > > > fabric8: http://fabric8.io/ > > > > > > > > > > > > > > > > > > > > >
