You could try with a * instead of specifying the namespace (in case
this is the problem).
Something like:
xpath("/*:part/*:message/node()")
Not sure if the problem comes from the xpath, but I would say so.
On Thu, Sep 11, 2008 at 6:39 PM, raulvk <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am using Camel to control the flow of validation, transformation and
> routing tasks that are applied to messages entering via ServiceMix CXF's
> Binding Component. The CXF consumer endpoint sends the message straightaway
> to Camel.
>
> When validating the incoming message, I realized that it is surrounded by
> the <jbi:message> wrapper.
> How can I get rid of it so as to send the ACTUAL XML message to Camel's
> validator?
>
> I have tried the following:
>
> - .setBody().xpath("//jbi:message/jbi:part/can:IncomingMessage",
> m).to("validator:file:///<schemaLocation>")
>
> AND
> . .transform().xpath("//jbi:message/jbi:part/can:IncomingMessage",
> m).to("validator:file:///<schemaLocation>")
>
> m is bound to a HashMap containing the NameSpace mappings.
>
> However, the result is always an empty XML Body, which provokes an exception
> at the Validator.
>
> Is there an easy way of EXTRACTING the XML payload?
>
> Thank you.
> --
> View this message in context:
> http://www.nabble.com/JBI-Wrapper-tp19439139s22882p19439139.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
