I suppose this declares the namespaces through the StaticContext. But
according to the XQuery spec, declaring them in the Prolog (leading section
of the XQuery expression file) should have the same effect. And it's easier
to maintain in the long run.
Regards,
Raúl.
On 6 Mar 2013 01:08, "Willem jiang" <willem.ji...@gmail.com> wrote:
> I just checked the code of camel-xquery component, it supports to set the
> namespaces through the uri.
> myNamespace is map instance which you need to bind it into CamelContext
> Registry.
>
> from("direct:transform-queue").
> to("xquery:transform.xqy?namespaces=#myNamespace").
> to("log:com.mydomain.TransformerRoute?level=INFO");
>
>
> --
> Willem Jiang
>
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> Web: http://www.fusesource.com | http://www.redhat.com
> Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
> (English)
> http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
>
>
>
>
> On Wednesday, March 6, 2013 at 7:18 AM, Phobos wrote:
>
> >
> > In principle that would appear to work as a filter, however in this
> instance
> > I am using the XQuery template as a transformer endpoint. For example;
> >
> > from("direct:transform-queue").
> > to("xquery:transform.xqy").
> > to("log:com.mydomain.TransformerRoute?level=INFO");
> >
> > Is there a way to inject custom namespaces into the above example (as an
> > endpoint)?
> >
> > Thanks
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/Camel-XQuery-Saxon-tp5728490p5728604.html
> > Sent from the Camel - Users mailing list archive at Nabble.com (
> http://Nabble.com).
>
>
>
>
