I was using Camel 2.3. I switched to version 2.4 as you recommended and the
error highlighting went away.
With version 2.4, it now works for '.filter().xpath("/order[not(@test)]")'
and also for Claus's suggestion of '.filter(xpath("/order[not(@test)]"))'.
Before trying the 2.4 version, I put the xpath logic in a custom Processor
which updates the header based on the xpath expression evaluations (of which
there could be many). Based on the header, the route will send it
accordingly.
I wanted to use the built-in filtering/evaluation support in Camel so I may
come back and put the filtering in the route itself (instead of using my
Processor). Camel is so flexible that I find it difficult to decide when to
use one approach over another!
I really appreciate the help!
--
View this message in context:
http://camel.465427.n5.nabble.com/Help-with-filter-behavior-tp2256745p2261890.html
Sent from the Camel - Users mailing list archive at Nabble.com.
