It takes an an (HTTP) URL to a XLST file, which is used to transform the XML content. The XSLT file may include absolute links to other files.
If you use MapForce to create your XSLT be aware that not all functions are compatible with our XSLT component.
Read more about Unsupported XSLT.
This component can not be used as the first component in a flow, since it expects to consume XML exchanges.
The XSLT component has the following configuration options:
|Path to XSLT file that defines the transformation
|A xslt file that has been uploaded to be used with the flow.
- You can't use both options in the XSLT component. You can only use one or the other.
- Using the
XSLT Filehas an advantage on the
URL. When using the
XSLT Fileproperty your xslt file are also versioned with your flow versions. That isn't the case when you use the
- The XSLT component has to be configured with an (HTTP) URL
It also has a
Compile XSLT button, that validates whether Dovetail can access the XSLT file and that the XSLT file is valid.
The XSLT component compiles the XSLT during installation and caches it. Changes to a XSLT file will not take effect unless an integration flow is re=depolyed/re-installed.
Special care with the XSLT
Any files referenced inside the XSLT must have an absolute http url that can be reached by Dovetail ESB, otherwise it will not be able to find these resources.
<!-- DON'T DO THIS -->
<xsl:with-param name="file" select="'./codeconversion.xml'" as="item()"/>
<!-- DO THIS INSTEAD! -->
<xsl:with-param name="file" select="'http://dovetail.example.local/xslt/codeconversion.xml'" as="item()"/>
Not all (Mapforce) XSLT functions or constructors are supported in this component. A hint that you are using an unsupported fucntion is an
undefined message when you try to compile the XSLT in its settings.
Our XSLT component uses the SaxParser library.
Known unsupported functions are:
Known unsupported constructors are: