Claus Ibsen-2 wrote > > Chained converters can be tricky as they can become non optimal, if > the intermediate conversion > takes time/memory etc. It would instead often be better to have A -> C > directly as converter. > True!
Claus Ibsen-2 wrote > > Also if there is multiple choices for the chain, which one to pick etc? > Simple tasks are no fun, right :)? Any way, my problem is that Ive written really simple context which transformed message by xpath component. The cxf payload type has been replaced by come apache Node (wrapper for some kind of iterator - sorry cannot recall full class name right now) and those node was not convertible out of the box when used in choice bean method invocation (w3c Document type). So camel's core components only were used. it is possible that some converters were not included (its camel test only) by default? Logs registered over 100 converters ready to use. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-converters-chaining-tp5719295p5719304.html Sent from the Camel - Users mailing list archive at Nabble.com.
