Name | Default Value | Description |
|---|
converter
| null
| Option to override default XmlConverter. Will lookup for the converter in the Registry. The provided converted must be of type org.apache.camel.converter.jaxp.XmlConverter. |
transformerFactory
| null
| Option to override default TransformerFactory. Will lookup for the transformerFactory in the Registry. The provided transformer factory must be of type javax.xml.transform.TransformerFactory. |
transformerFactoryClass
| null
| Option to override default TransformerFactory. Will create a TransformerFactoryClass instance and set it to the converter. |
uriResolverFactory
| DefaultXsltUriResolverFactory | Camel 2.17: Reference to a org.apache.camel.component.xslt.XsltUriResolverFactory which creates an URI resolver per endpoint.The default implementation returns an instance of org.apache.camel.component.xslt.DefaultXsltUriResolverFactory which creates the default URI resolver org.apache.camel.builder.xml.XsltUriResolver per endpoint. The default URI resolver reads XSLT documents from the classpath and the file system. This option instead of the option uriResolver shall be used when the URI resolver depends on the resource URI of the root XSLT document specified in the endpoint; for example, if you want to extend the default URI resolver. This option is also available on the XSLT component, so that you can set the resource resolver factory only once for all endpoints. |
uriResolver
| null
| Camel 2.3: Allows you to use a custom javax.xml.transformation.URIResolver. Camel will by default use its own implementation org.apache.camel.builder.xml.XsltUriResolver which is capable of loading from classpath. |
resultHandlerFactory
| null
| Camel 2.3: Allows you to use a custom org.apache.camel.builder.xml.ResultHandlerFactory which is capable of using custom org.apache.camel.builder.xml.ResultHandler types. |
failOnNullBody
| true
| Camel 2.3: Whether or not to throw an exception if the input body is null. |
deleteOutputFile
| false
| Camel 2.6: If you have output=file then this option dictates whether or not the output file should be deleted when the Exchange is done processing. For example suppose the output file is a temporary file, then it can be a good idea to delete it after use. |
output
| string
| Camel 2.3: Option to specify which output type to use. Possible values are: string, bytes, DOM, file. The first three options are all in memory based, where as file is streamed directly to a java.io.File. For file you must specify the filename in the IN header with the key Exchange.XSLT_FILE_NAME which is also CamelXsltFileName. Also any paths leading to the filename must be created beforehand, otherwise an exception is thrown at runtime. |
contentCache
| true
| Camel 2.6: 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.
Note: from Camel 2.9 a cached stylesheet can be forced to reload at runtime via JMX using the clearCachedStylesheet operation. |
allowStAX
| | Camel 2.8.3/2.9: Whether to allow using StAX as the javax.xml.transform.Source. The option is default false in Camel 2.11.3/2.12.2 or older. And default true in Camel 2.11.4/2.12.3 onwards. |
transformerCacheSize
| 0
| Camel 2.9.3/2.10.1: The number of javax.xml.transform.Transformer object that are cached for reuse to avoid calls to Template.newTransformer(). |
saxon
| false
| Camel 2.11: Whether to use Saxon as the transformerFactoryClass. If enabled then the class net.sf.saxon.TransformerFactoryImpl. You would need to add Saxon to the classpath. |
saxonExtensionFunctions
| null | Camel 2.17: Allows to configure one or more custom net.sf.saxon.lib.ExtensionFunctionDefinition. You would need to add Saxon to the classpath. By setting this option, saxon option will be turned out automatically. |
errorListener
| | Camel 2.14: Allows to configure to use a custom javax.xml.transform.ErrorListener. Beware when doing this then the default error listener which captures any errors or fatal errors and store information on the Exchange as properties is not in use. So only use this option for special use-cases. |
