Re: Xpath parameter binding NodeList vs. Node

2013-08-28 Thread Claus Ibsen
I logged a ticket about this https://issues.apache.org/jira/browse/CAMEL-6674 On Wed, Aug 28, 2013 at 8:04 AM, Claus Ibsen wrote: > Hi > > When you have Node as the type. Can you try test > > a) > first with a use-case where there is only 1 element. And then onwards, > 0 or 2+ elements? > > b) >

Re: Xpath parameter binding NodeList vs. Node

2013-08-27 Thread Claus Ibsen
Hi When you have Node as the type. Can you try test a) first with a use-case where there is only 1 element. And then onwards, 0 or 2+ elements? b) And then do another test where the first use-case has 2+ elements,. and then 1 element. I suspend in (b) Camel regards the type converter NodeList -

Re: Xpath parameter binding NodeList vs. Node

2013-08-27 Thread ychawla
Hi Raul, Thanks for you reply. The query returns exactly one node. To retrieve the node, I do something like this: Node containerNode = containerNodeList.item(0); The OJBCamelXpath annotation is a class like this: @Retention(RetentionPolicy.RUNTIME) @Target({ElementType.FIELD, ElementType.METHO

Re: Xpath parameter binding NodeList vs. Node

2013-08-27 Thread Raul Kripalani
I wonder if your XPath is returning zero nodes. Try to find out the length of the NodeList with the getLength method. What exactly is this @OJBCamelXPath annotation? And how does it recognise namespace "foo"? You don't seem to declare it (unless the custom annotation is taking care of it somehow -