I am having a similar issue and cannot get my xslt route to use my custom
uriResolver.
I put into the headers the location of a webservice that will return back
the xsl:
headers.put("templateLocation",
"http://localhost:8080/path/to/stylesheet";);
then in my route try and do the following:
.rec
Ok, worked it out - it was due to the XPath having already accessed the
'stream' before the XSL was used. adding streamCache ('') 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 mail
The above was working for a hard coded XSL name:
META-INF/xsl/5.xsl
what i need to do i dynamically generate the name of the xsl:
concat('META-INF/xsl/',//phar:pharmacyInfoRequest/pharmacyId/text(),'.xsl')
when i use
XPath (put the name into a header) + recipientList + XSLT should work.
Best,
Christian
Am 16.01.2013 12:56 schrieb "sammm" :
> i'm new to Camel and have seen the example etc and the 'How do I use
> dynamic
> URI in To' posting and infor on Expressions etc.
> What i need to do, and cant quite work
