3

Is there a way to tell Camel to use the Saxon library by default, so I would not need to specify it in every XLST transformation? E.g.:

.to("xslt:my-file.xsl?transformerFactoryClass=net.sf.saxon.TransformerFactoryImpl")

Specifying it in every endpoint makes code less readable.

I've seen suggestions (though in some other contexts) on setting environment property:

javax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl

Would this somehow be possible to be set within single camel context?

P.S. I am using Camel 2.10, so the saxon parameter suggestion is unfortunately not an option yet...

Laimoncijus
  • 8,615
  • 10
  • 58
  • 81
  • How did you resolve it? I'm using camel 2.6 – Marcin Erbel Jul 21 '15 at 14:39
  • 1
    @MarcinErbel: eventually we moved to newer camel version and are using `saxon` property. I think there is no other way... - either specifying option per endpoint or via system property for whole JVM... – Laimoncijus Aug 05 '15 at 07:06

2 Answers2

5

According to the documentation you can use:

.to("xslt:my-file.xsl?saxon=true")

which is much more readable

Matthew Wilson
  • 2,045
  • 14
  • 27
  • 2
    sorry, forgot to that say I am using camel 2.10, the `saxon` parameter is available as of 2.11... thanks for the answer! – Laimoncijus Apr 11 '14 at 15:59
2

The system property setting is working for the whole JVM, it is not good way for the container setting.

You can extend the XsltComponent to set the transformerFactoryClass for you as camel-2.11.x does or you can just add an constant which hold the option of transformerFactoryClass.

Willem Jiang
  • 3,291
  • 1
  • 14
  • 14