________________________________

From: Yuzo Fujishima [mailto:fuji...@bc.jp.nec.com] Sent: Sat 6/4/2005 8:11 AM To: Satish Thatte; wsbpeltc Cc: Assaf Arkin; Danny van der Rijn; Charlton Barreto Subject: Re: [wsbpel] Issue - 157 - Proposal For Vote

I don't quite see what are the problems.

I've written an example and attached the files used. (Apply assign.xsl to var1.xml. Then you'll get newVar1.xml.)

Suppose we want to assign from var2 and var3 to var1.

In that case, we write something similar to assign.xsl (excluding the variable binding part) within an assign activity. Perhaps we should rename the activity to "transform".

The activity should look like below:

<transform variable="var1"> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="orderNumber"> <xsl:element name="orderNumber"> <xsl:value-of select="$var2/purchaseOrder/orderNumber"/> </xsl:element> </xsl:template> <xsl:template match="billingAddress"> <xsl:element name="billingAddress"> <xsl:copy-of select="$var3/customers/customer[ @id=$var2/purchaseOrder/buyerId]/address/*"/> </xsl:element> </xsl:template> <xsl:template match="@*|node()"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> </xsl:stylesheet> </transform>

Those parts of var1 that need not be modified are copied by <xsl:template match="@*|node()"> template. Pretty simple and idiomatic.

I noticed that the use of XSLT may sometimes result in more efficient (rather than inefficient) processing because multiple assigns can be bunched together to form one transformation.

How do you like above?

Satish Thatte wrote: