Page Comparison

The FastXSLT Mediator is similar to the XSLT mediator, but it uses the Streaming XPath Parser and applies the XSLT transformation to the message stream instead of to the XML message payload. The result is a faster transformation, but you cannot specify the source, properties, features, or resources as you can with the XSLT mediator. Therefore, the FastXSLT mediator is intended to be used with messages that are not being built before the mediator receives the messageto gain performance in cases where the original message remains unmodified. Any pre-processing performed on the message payload will not be visible to the FastXSLT mediator, because the transformation logic is applied on the original message stream instead of the message payload. In cases where the message payload needs to be pre-processed, use the XSLT mediator instead of the FastXSLT mediator.

For example, if you are using the VFS transport to handle files, you might want to read the content of the file as a stream and directly send the content for XSLT transformation. If you need to pre-process the message payload, such as adding or removing properties, use the XSLT mediator instead.

Following In summary, following are the key differences between the XSLT and FastXSLT mediators:

...

• Performs XSLT transformations on the message stream.
• The message is not built before processing, so any pre-processing on the message will not be reflected in the XSLT transformation.
• Provides faster performance than the XSLT mediator.

...

• mediator.

To enable the FastXSLT mediator, your XSLT script must include the following parameter in the XSL output:

<xsl:output method="xml" omit-xml-declaration="yes" encoding="UTF-8" indent="yes"/>

...