On Wed, Oct 3, 2012 at 9:33 PM, Christian Müller <christian.muel...@gmail.com> wrote: > E.g. convert the body into a dom, sax or stax source and do whatever you > need to do. >
Yes or use some XPath API to grab whatever you need. In fact you can use the @XPath bean parameter binding if you want Camel to do that for you. Or just grab the XPathBuilder API and use that. Or use the vanilla XPath API from the JDK. > Best, > Christian > > Sent from a mobile device > Am 02.10.2012 23:46 schrieb "suralk" <sura.mon...@yahoo.com>: > >> Hi Christian, >> I am using the Camel CXF component with the MESSAGE dataFormat (using >> PAYLOAD throws an exception, so have to stick with MESSAGE format with >> respect to this particular web service). >> >> Similar to balkishore, I do not want to set any header based on the >> extracted soap element. Rather, I want to extract out these soap elements >> and use them for some other processing work. However, as I understand, >> XPath >> or XQuery do not support this. They can only be used to set headers, or as >> filter conditions. >> In this context, what options do we have to extract out elements in the >> soap >> response in MESSAGE mode? >> I currently convert the response explicitly to an xml file, but this is not >> very elegant. >> >> >> >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Getting-a-node-from-an-XML-using-camel-cxf-tp5720008p5720401.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen