Re: Dynamic XSL from Content

2013-08-02 Thread ericsodt
: .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

Re: Dynamic XSL from Content

2013-01-18 Thread sammm
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

Re: Dynamic XSL from Content

2013-01-17 Thread sammm
-- 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.

Dynamic XSL from Content

2013-01-16 Thread sammm
.465427.n5.nabble.com/Dynamic-XSL-from-Content-tp5725634.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Dynamic XSL from Content

2013-01-16 Thread Christian Müller
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.