XSLT transformer
Transforms XML messages using an XSLT stylesheet.
Transforms XML messages using an XSLT stylesheet.
Transforms the following message payload types:
String
- results in String
message
org.w3c.dom.Document
- results in org.w3c.dom.Document
message
javax.xml.transform.Source
- results in javax.xml.transform.Result
.
Specify a result transformer to convert to this result to another XML format
Custom transformation
Custom transformation will allow you to specify the location of the resource.
By default this will be the resource folder.
Transformation location
Filename of the XSLT stylesheet file, including the location.
For example: resources/my-transformation.xsl
XML Transformation
Select the xml mapping that will be used to transform your xml message.
This can either be an XML mapping or an xslt.
You can create new xml mappings in the resources tab.
Result transformer
Transformer that transforms the result to an alternative (XML) format before it is send on the channel.
This only works when the input message payload is a java.xml.transform.Source
or a result factory is specified, otherwise this transformer does nothing.
If you want to generate a PDF document using XSL-FO, provide a FOP XSL-FO result transformer here (and also set the correct result factory).
Result factory
A result factory can prepare the XSLT transformation for a specific output format. Normally, when transforming XML to XML, no result factory is needed.
If you want to generate a PDF document using XSL-FO however, provide a FOP XSL-FO result factory here (and also set the correct result transformer).
Transformer factory class
A fully qualified class name to a transformer factory class that overrides the current JVM default.
XSLT param headers
Very often to assist with transformation you may need to have access to message data. For example, you may need to get access to certain message headers and pass them on as parameters to a transformer.
If message header names match 1:1 to parameter names, you can simply use this property. It's also possible to use wildcards for simple pattern matching which supports the following simple pattern styles: xxx
, xxx
, xxx
and xxx*yyy
.
Very often to assist with transformation you may need to have access to message data. For example, you may need to get access to certain message headers and pass them on as parameters to a transformer.
With this option you can specify an expression or a value:
An expression should be any valid SpEL expression with Message
being the root object of the expression evaluation context. It is also possible to reference any component in a flow using the @
notation, e.g. @'full.id.of.your.flow.component'
. This can be very useful for passing XSLT extention gateways as parameters to your XSLT.
A value allows you to specify a simple scalar value. You can also use property placeholders (e.g. ${some.value}
).
Output channel
Channel where output messages should be sent after (successfully) processing the input message.
You can select the nullChannel
here to silently drop the output messages.
Required
Input channel
Channel to consume the input messages from.
Required
Id
Name that uniquely identifies this flow component.
Required