Hi Yeah we love contributions. See here http://camel.apache.org/contributing.html
On Fri, Jul 12, 2013 at 10:58 AM, per.ce...@gmail.com <per.ce...@gmail.com> wrote: > 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. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen