By Juergenkress-Oracle on Jul 29, 2016
(For a quick introduction to the graphical views in the 12c XSLT Editor see here.)
XSLT View provides the ability to edit any XSLT file graphically. It is intended for XSLT developers who have a general understanding of XSLT and have written XSLT source code in a text editor.
XSLT View is effectively a graphical source view. It has many advantages over editing XSLT source in a text editor. Many of these are listed in the XSLT Editor Overview at the link above. I think the best way to show these advantages is through specific examples. In this post I will use an identity template to create a complex XSLT map.
For our example we will work with a PurchaseOrder to PurchaseOrder map.
Our goal for this map is to copy the source tree to the target tree, and while we are doing the copy, we want to copy the ShipTo CustomerName value into the BillTo Address, so that when we are done, the ShipTo and BillTo elements will both use the same CustomerName.
We could do
this by explicitly mapping each node, however, we can also use an
identity template to copy the source. Identity templates are often used
to copy an input document to the output document, but make some
modification while the copy is being done. If the source input at
runtime is small compared to the number of elements defined in the
source schema, it can be significantly faster to copy the tree using an
identity template, compared to creating explicit XSLT statements for
every node in the schema. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.