Ok, worked it out - it was due to the XPath having already accessed the
'stream' before the XSL was used. adding streamCache ('<route
streamCache="true">') fixed it.

Martin



--
View this message in context: 
http://camel.465427.n5.nabble.com/Dynamic-XSL-from-Content-tp5725634p5725755.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to