camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <>
Subject Re: Camel, Spring, routeContextRef and namespaces?
Date Tue, 10 May 2011 08:16:40 GMT
Here is away to do the job by using the Java DSL.
You can find an unit test for it here[1]



On 2/17/11 7:32 AM, tecoripa wrote:
> Unfortunately, no.  I've been wrestling with a similar issue all day long.
> The atom messages I receive set the default namespace, i.e.:
> <entry xmlns="">
> ...
> </entry>
> and although I no longer get the XPath error, my xpath expressions don't get
> resolved -- results are always null.
> The expression "/atom:entry/atom:title" throws an error, since the namespace
> prefix does not get inherited from my root<beans xlmns:atom=...>
> declaration. The expression "/entry/title" gets parsed correctly, but never
> results in a match.
> If you find a solution, please post it.  I suspect declaring the namespace
> in the<camelContext>  element results in the Namespace being set under the
> hood when processing that element's tree, but no such processing takes place
> for the<routeContext>  tag.  I'm going to try a few more things out, then
> roll up my sleeves and take a look at the source code.

Blog: (English)
Twitter: willemjiang

Connect at CamelOne May 24-26
The Open Source Integration Conference

View raw message