Hi again,
Is this problem existing, due to camels own XsltUriResolver?
It seems that camels XsltUriResolver only is capable to handle files
either from the classpath or the file system.
With the xlst function, document(''), the xslt processer should be able to
handle that the result "is the source XML of the XSLT document itself".
Should I create a JIRA case for camel? Is there any guidelines how to
proceed?
Regards / Per
--
View this message in context:
http://camel.465427.n5.nabble.com/xslt-TransformerException-include-href-is-empty-tp5730288p5735567.html
Sent from the Camel - Users mailing list archive at Nabble.com.
