Hi A bit odd. I added unit tests to camel-jms which works http://svn.apache.org/viewvc?rev=998598&view=rev
And could you double check that there is no old versions of camel in the classpath? And the data you send is valid XML Also when you get that exception, is there a JMS header with the key foo? And what type is that header? Is it a boolean or a String type? On Sat, Sep 18, 2010 at 8:56 PM, Illtud Daniel <illtud.dan...@llgc.org.uk> wrote: > On 18/09/10 07:19, Claus Ibsen wrote: >> >> You have header >>> >>> <header>$foo = 'true'</header> >> >> But you should use xpath >> <xpath>$foo = 'true'</xpath> > > Sorry, I cut and pasted in the route that I attempted to > fix this problem. > > My original was indeed <xpath>$foo = 'true'</xpath> > and that gave the error: > > 2010-09-18 01:59:36,205 | ERROR | Failed delivery for exchangeId: >> ID:vaio-51221-1284757417176-5:22:-1:1:1. Exhausted after delivery attempt: >> 1 >> caught: org.apache.camel.builder.xml.InvalidXPathExpression: Invalid >> xpath: >> $foo = 'true'. > > Has something changed between camel 2.0 & 2.4.0? Is that still > the proper way to match on headers (using xpath?). It doesn't > work for me anymore. > > -- > Illtud Daniel illtud.dan...@llgc.org.uk > Prif Swyddog Technoleg Chief Technical Officer > Llyfrgell Genedlaethol Cymru National Library of Wales > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
