XSLT Saxon

Transform XML payloads using an XSLT template using Saxon.

What’s inside

XSLT Saxon component, URI syntax: xslt-saxon:resourceUri

Please refer to the above links for usage and configuration details.

Maven coordinates

<dependency>
    <groupId>org.apache.camel.springboot</groupId>
    <artifactId>camel-xslt-saxon-starter</artifactId>
</dependency>

Spring Boot Auto-Configuration

The starter supports 14 options, which are listed below.

Name	Description	Default	Type
camel.component.xslt-saxon.allow-template-from-header	Whether to allow to use resource template from header or not (default false). Enabling this allows to specify dynamic templates via message header. However this can be seen as a potential security vulnerability if the header is coming from a malicious user, so use this with care.	false	Boolean
camel.component.xslt-saxon.autowired-enabled	Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.	true	Boolean
camel.component.xslt-saxon.content-cache	Cache for the resource content (the stylesheet file) when it is loaded. If set to false Camel will reload the stylesheet file on each message processing. This is good for development. A cached stylesheet can be forced to reload at runtime via JMX using the clearCachedStylesheet operation.	true	Boolean
camel.component.xslt-saxon.enabled	Whether to enable auto configuration of the xslt-saxon component. This is enabled by default.		Boolean
camel.component.xslt-saxon.lazy-start-producer	Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.	false	Boolean
camel.component.xslt-saxon.saxon-configuration	To use a custom Saxon configuration. The option is a net.sf.saxon.Configuration type.		Configuration
camel.component.xslt-saxon.saxon-configuration-properties	To set custom Saxon configuration properties		Object>
camel.component.xslt-saxon.saxon-extension-functions	Allows you to use a custom net.sf.saxon.lib.ExtensionFunctionDefinition. You would need to add camel-saxon to the classpath. The function is looked up in the registry, where you can use commas to separate multiple values to lookup.		String
camel.component.xslt-saxon.secure-processing	Feature for XML secure processing (see javax.xml.XMLConstants). This is enabled by default. However, when using Saxon Professional you may need to turn this off to allow Saxon to be able to use Java extension functions.	true	Boolean
camel.component.xslt-saxon.transformer-factory-class	To use a custom XSLT transformer factory, specified as a FQN class name		String
camel.component.xslt-saxon.transformer-factory-configuration-strategy	A configuration strategy to apply on freshly created instances of TransformerFactory. The option is a org.apache.camel.component.xslt.TransformerFactoryConfigurationStrategy type.		TransformerFactoryConfigurationStrategy
camel.component.xslt-saxon.uri-resolver	To use a custom UriResolver. Should not be used together with the option 'uriResolverFactory'. The option is a javax.xml.transform.URIResolver type.		URIResolver
camel.component.xslt-saxon.uri-resolver-factory	To use a custom UriResolver which depends on a dynamic endpoint resource URI. Should not be used together with the option 'uriResolver'. The option is a org.apache.camel.component.xslt.XsltUriResolverFactory type.		XsltUriResolverFactory
camel.component.xslt-saxon.xpath-total-op-limit	Limits the total number of XPath operators in an XSL Stylesheet. The default (from JDK) is 10000. Configuring this corresponds to setting JVM system property: jdk.xml.xpathTotalOpLimit	10000	Integer

Name

Description

Default

Type

camel.component.xslt-saxon.allow-template-from-header

Whether to allow to use resource template from header or not (default false). Enabling this allows to specify dynamic templates via message header. However this can be seen as a potential security vulnerability if the header is coming from a malicious user, so use this with care.

false

Boolean

camel.component.xslt-saxon.autowired-enabled

Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.

true

Boolean

camel.component.xslt-saxon.content-cache

Cache for the resource content (the stylesheet file) when it is loaded. If set to false Camel will reload the stylesheet file on each message processing. This is good for development. A cached stylesheet can be forced to reload at runtime via JMX using the clearCachedStylesheet operation.

true

Boolean

camel.component.xslt-saxon.enabled

Whether to enable auto configuration of the xslt-saxon component. This is enabled by default.

Boolean

camel.component.xslt-saxon.lazy-start-producer

Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing.

false

Boolean

camel.component.xslt-saxon.saxon-configuration

To use a custom Saxon configuration. The option is a net.sf.saxon.Configuration type.

Configuration

camel.component.xslt-saxon.saxon-configuration-properties

To set custom Saxon configuration properties

Object>

camel.component.xslt-saxon.saxon-extension-functions

Allows you to use a custom net.sf.saxon.lib.ExtensionFunctionDefinition. You would need to add camel-saxon to the classpath. The function is looked up in the registry, where you can use commas to separate multiple values to lookup.

String

camel.component.xslt-saxon.secure-processing

Feature for XML secure processing (see javax.xml.XMLConstants). This is enabled by default. However, when using Saxon Professional you may need to turn this off to allow Saxon to be able to use Java extension functions.

true

Boolean

camel.component.xslt-saxon.transformer-factory-class

To use a custom XSLT transformer factory, specified as a FQN class name

String

camel.component.xslt-saxon.transformer-factory-configuration-strategy

A configuration strategy to apply on freshly created instances of TransformerFactory. The option is a org.apache.camel.component.xslt.TransformerFactoryConfigurationStrategy type.

TransformerFactoryConfigurationStrategy

camel.component.xslt-saxon.uri-resolver

To use a custom UriResolver. Should not be used together with the option 'uriResolverFactory'. The option is a javax.xml.transform.URIResolver type.

URIResolver

camel.component.xslt-saxon.uri-resolver-factory

To use a custom UriResolver which depends on a dynamic endpoint resource URI. Should not be used together with the option 'uriResolver'. The option is a org.apache.camel.component.xslt.XsltUriResolverFactory type.

XsltUriResolverFactory

camel.component.xslt-saxon.xpath-total-op-limit

Limits the total number of XPath operators in an XSL Stylesheet. The default (from JDK) is 10000. Configuring this corresponds to setting JVM system property: jdk.xml.xpathTotalOpLimit

10000

Integer