SELECTING FROM AVAILABLE SCRIPTING LANGUAGES
An XSLT call template builds one or more output nodes from scratch. The two XSLT scripting methods differ in whether or not an input parameter can be used.
Inline XSLT, accepts input via XPATH queries but does not accept input parameters. XSLT call templates accept input via both methods. The XPATH query you will see in the inline XSLT discussion is the same type as would be used in the XSLT call template
Simple XPATH queries are especially useful when creating outbound EDI segments like the REF or DTM segments, because you can collect data from source nodes that are not in the current context node of your source data and use this data to create repeating instances of a single output node.
Inline XSLT scripts are different from those created with the other scripting languages, because they do not use input parameters.
Here are two notes to keep in mind when working with XSLT call templates and inline XSLT.
First, when input parameters are used in an XSLT call template, the input values arrive through links from the source nodes to the Scripting functoid. If the source data is in a loop, the value input to the Scripting functoid depends on how many times the loop has been accessed before the script is executed. Second, when you
need a system variable such as System Date as input, you may have to use a call template and not inline XSLT. Releases of BizTalk that do not use Version 2.0 or higher of XSLT do not have access to XSLT functions that can access system variables.
An XSLT call template builds one or more output nodes from scratch. The two XSLT scripting methods differ in whether or not an input parameter can be used.
Inline XSLT, accepts input via XPATH queries but does not accept input parameters. XSLT call templates accept input via both methods. The XPATH query you will see in the inline XSLT discussion is the same type as would be used in the XSLT call template
Simple XPATH queries are especially useful when creating outbound EDI segments like the REF or DTM segments, because you can collect data from source nodes that are not in the current context node of your source data and use this data to create repeating instances of a single output node.
Inline XSLT scripts are different from those created with the other scripting languages, because they do not use input parameters.
Here are two notes to keep in mind when working with XSLT call templates and inline XSLT.
First, when input parameters are used in an XSLT call template, the input values arrive through links from the source nodes to the Scripting functoid. If the source data is in a loop, the value input to the Scripting functoid depends on how many times the loop has been accessed before the script is executed. Second, when you
need a system variable such as System Date as input, you may have to use a call template and not inline XSLT. Releases of BizTalk that do not use Version 2.0 or higher of XSLT do not have access to XSLT functions that can access system variables.
No comments:
Post a Comment