:
.recipientList(simple(header(templateLocation)+?uriResolver=#emailResolver)
Any thoughts on how I might be able to dynamically load my xsl and process
it through the uri resolver?
Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Dynamic-XSL-from-Content-tp5725634p5736705
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
--
View this message in context:
http://camel.465427.n5.nabble.com/Dynamic-XSL-from-Content-tp5725634p5725729.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.465427.n5.nabble.com/Dynamic-XSL-from-Content-tp5725634.html
Sent from the Camel - Users mailing list archive at Nabble.com.
a header can be set, maybe thats the way to go - again
can that be doen using DSL?
Thanks for the help
Martin
--
View this message in context:
http://camel.465427.n5.nabble.com/Dynamic-XSL-from-Content-tp5725634.html
Sent from the Camel - Users mailing list archive at Nabble.com.