<xslt>
Syntax
<xslt name='simon'
xslurl="https://www.intersystems.com/transform.xsl"
source="context.a" target="context.b">
<parameters>
<parameter name="surname" value="sez"/>
</parameters>
</xslt>
Attributes and Elements
Required. URI of the XSLT definition that controls the transformation. The URI may begin with one of the following strings: “file:” “http:” “url:” or “xdata:” Specify a string of up to 255 characters.
Required. Name of the source (stream) object. Specify a string of up to 255 characters.
Required. Name of the target (stream) object Specify a string of up to 255 characters.
An optional <parameters> element may appear. Inside the <parameters> container, zero or more <parameter> elements may appear. Each <parameter> element defines an XSLT name-value pair to pass to the stylesheet that controls the XSLT transformation.
Specifies whether the XSLT transformation uses XSLT 1.0 or 2.0. Specify either "1.0" or "2.0"
Description
The <xslt> element allows you to apply an XSLT transformation during a business process. The <xslt> element transforms an input stream to an output stream via an arbitrary XSLT definition. The XSLT definition may be in an external file, or it may be defined in a class in the same namespace as the BPL business process.
The source and target stream objects must be declared as properties of the context object for the business process. The context object is a general-purpose data container for the business process. You may define context properties by providing <context> and <property> elements at the beginning of the <process> element. That done, you may refer to these properties anywhere inside the <process> element using dot syntax, as in: context.MyInputStream or context.MyOutputStream
The xslurl string is a URI that identifies the location of the XSLT definition. The xslurl value may begin with one of the following strings:
file: http: url: xdata:
Where file:, http:, and url: have the standard meanings. An xdata: string takes this form:
xdata://PackageName.ClassName:XDataName
Where:
-
PackageName.ClassName identifies a class in the same namespace as the BPL business process.
-
XDataName is the name of an XData block within that class that contains the XSLT definition for this <xslt> statement. This convention allows XSLT definitions to be stored inside InterSystems IRIS classes, as an efficient alternative to storing them outside InterSystems IRIS in the local file system or on the Web.
If the XSLT requires parameters, include them in a <parameters> block within the <xslt> element.
