Hi I would only suggest xslt if you have experience using it and are comfortable using it. It can be really hard to understand and maintain if it gets big.
Plain java code, even if its doing boiler plate get -> set is something everybody understands and can maintain. And there is some libraries like dozer (and others) that can do POJO -> POJO mapping, if that is required. That is just my thoughts. On Thu, Jan 22, 2015 at 3:20 PM, bharadwaj <bharadwaj2...@gmail.com> wrote: > Camel - provides users java code free environment , it has various components > to fulfill users requirement. > > The best way is to use XQuey?XSLT to form INBOUND / OUTBOUND messages. > > While XQuery can be used for simple transformations, it lacks the power and > sofistication of XSLT (especially templates and the <xsl:apply-templates> > instruction). > > XSLT is a language that was especially designed to process tree structures. > It is still best at doing this. > > In cases when accessing an XML database it would be a good decision to use > (the efficiency of) XQuery to extract the necessary XML nodes and then do > the transformation with XSLT from here on. Some XSLT 2.x / XQuery processors > do allow this (via extensions) even now. The next wave of XSLT 2.x/XQuery > 1.x specifications will most probably make such interoperability an official > feature of these languages. > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Choosing-between-Mapping-Options-tp5761977p5762022.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
