Hallo camel community, I just upgraded from camel 2.13.2 to 2.14.0.
Camel git commit 1b38aad342529e98b5f76e11029ec50b1768949f (CAMEL-7753: xslt component - Store warning/errors etc as exchange properties so end users can get hold of those. Now works with camel-saxon also.) of 27-aug-2014 introduced saxonReceiverClass and saxonWarnerClass and a check in doStart method for the existence of "net.sf.saxon.event.Receiver" and "net.sf.saxon.serialize.MessageWarner" in ...\camel-core\src\main\java\org\apache\camel\builder\xml\XsltBuilder.java. I assume that these classes are available Saxon-HE jar 9.6.x but not in the Saxon 8.7 library and that's a problem for me. I get an error when starting camel: Error pre-loading Saxon classes. Make sure you have saxon on the classpath, and the classloader can load the following two classes: net.sf.saxon.event.Receiver, net.sf.saxon.serialize.MessageWarner. I can't use the Saxon-HE because I use a lot of java calls inside xslt (eg to set message headers) and java calls are not supported in Saxon-HE home edition. That the reason why I use the full Saxon which is version 8.7 for now. Is there a solution to this problem? -- Kind regards, Ronny Aerts<mailto:[email protected]> - Intris nv - Wapenstilstandlaan 47, 2600 Berchem, Belgium R&D Integration Architect Prince II<http://en.wikipedia.org/wiki/PRINCE2> certified - ITIL<http://en.wikipedia.org/wiki/Information_Technology_Infrastructure_Library> certified Tel: +32-3-326.50.75 Intris nv Wapenstilstandlaan 47 B-2600 Berchem Tel. +32 3 326 50 75 Fax +32 3 326 42 23 www.intris.be<http://www.intris.be/> [http://www.intris.be/mail/AEO_Sticker_108pxRGB.jpg] <http://www.intris.be> DISCLAIMER This is an e-mail from Intris. The information contained in this communication is intended solely for use by the individual or entity to whom it is addressed. Use of this communication by others is prohibited. If the e-mail message was sent to you by mistake, please notify [email protected]<mailto:[email protected]>, destroy it without reading, using, copying or disclosing its contents to any other person. We accept no liability for damage related to data and/or documents which are communicated by electronic mail.
