On Fri, Feb 18, 2011 at 5:04 PM, Naira & Kobo <[email protected]> wrote: > > How do I stop implicit call to a custom type converter made by camel. > > see my script below: > > <route id="kimonoTransactionProcessor"> > <from > uri="vm:endpoint1?concurrentConsumers={{vmConConsumers}}"/> > <convertBodyTo type="org.company.customConverter" /> > <to uri="vm:endpoint2?timeout={{vm-timeout}}"/> > </route> > > I turned on traces on the custom converter and I realize after the first > (explicit) call to the customConverter - which converts from String to a > bean - class, camel implicitly calls the converter (to change from the new > bean to a string body type) just before calling endpoiint2. > > This needlessly causes unnecessary overhead. Is there a way to prevent this > call?
The trace logging may cause that 2nd conversion as it has to log it as a String. Camel will send the message with the type it is when sending to the VM endpoint. There is no type conversion forced there. > > kr. > -- > View this message in context: > http://camel.465427.n5.nabble.com/How-to-stop-implicit-call-to-Type-Converters-tp3391321p3391321.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
