Did you have chance to call the start of MarshalProcessor? I don't see any thing wrong from your route.
-- 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 Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Thursday, February 21, 2013 at 2:20 AM, khong07 wrote: > Hi, > > I don't marshal in seda:next route because in seda:next route, i'll > unmarshal. > > from("seda:next").unmarshal().json(JsonLibrary.Jackson).to(...); > > So, i must marshal before sending to seda:next, that why i want using a > ProducerTemplate.sendCallBack and call a MarshalProcessor inside Processor. > > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/marshal-with-MarshalProcessor-tp5727842p5727895.html > Sent from the Camel - Users mailing list archive at Nabble.com > (http://Nabble.com). >
