[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [no subject]
------_=_NextPart_001_01C56AF7.783B32A7 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD><TITLE>Message</TITLE> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <META content=3D"MSHTML 6.00.2900.2627" name=3DGENERATOR></HEAD> <BODY text=3D#000000 bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2><FONT face=3D"Times New Roman"><FONT = size=3D3><SPAN=20 class=3D160261800-07062005>> </SPAN>BTW, can someone show me an XSLT=20 implementation that will actually modify the source tree without = generating a=20 seperate result tree? </FONT></FONT></FONT></DIV> <DIV><FONT face=3DArial size=3D2><FONT><FONT face=3D"Times New = Roman"><FONT=20 size=3D3><SPAN class=3D160261800-07062005>> </SPAN>(Please read my = quotation from=20 XSLT spec: "<U>The result tree is <B>separate</B> from the source = tree</U>.").=20 If that XSLT implementation does not violate the spec, I don't know what = implementation will violate the spec. :-) </FONT><SPAN=20 class=3D160261800-07062005><FONT face=3DArial=20 size=3D2> </FONT></SPAN></FONT></FONT></FONT></DIV> <DIV><FONT face=3DArial size=3D2><FONT><FONT face=3D"Times New = Roman"><SPAN=20 class=3D160261800-07062005></SPAN></FONT></FONT></FONT> </DIV> <DIV><FONT face=3DArial size=3D2><FONT><FONT face=3D"Times New = Roman"><SPAN=20 class=3D160261800-07062005><FONT size=3D3>I think the crucial point here = is that we=20 are not looking at XSLT in abstract but in the context of BPEL. After = the=20 "new" tree is assigned to the variable, the original source tree is = simply=20 gone from the BPEL</FONT> <FONT size=3D3>process without leaving = any trace.=20 So the question of whether the XSLT transform modified the original tree = or not=20 has no answer, because the original tree is=20 gone.</FONT></SPAN></FONT></FONT></FONT></DIV> <DIV><FONT face=3DArial size=3D2><FONT><FONT face=3D"Times New Roman" = size=3D3><SPAN=20 class=3D160261800-07062005></SPAN></FONT></FONT></FONT> </DIV> <DIV><FONT><FONT><FONT face=3DArial size=3D2><SPAN = class=3D160261800-07062005>From=20 BPEL's point of view, BPEL simply cannot tell whether the tree = assigned to the variable is really a new tree or just a modification of = the=20 original one.</SPAN></FONT></FONT></FONT></DIV> <DIV><FONT><FONT><FONT face=3DArial size=3D2><SPAN=20 class=3D160261800-07062005></SPAN></FONT></FONT></FONT> </DIV> <DIV><FONT><FONT><FONT face=3DArial size=3D2><SPAN = class=3D160261800-07062005>So it=20 seems to me that, in this specific context, both XSLT and BPEL should be = happy=20 at the end of the assign ;-).</SPAN></FONT></FONT></FONT></DIV> <DIV><FONT><FONT><FONT face=3DArial size=3D2><SPAN=20 class=3D160261800-07062005></SPAN></FONT></FONT></FONT><FONT = face=3DArial=20 size=3D2><FONT><FONT face=3D"Times New Roman" size=3D3><SPAN=20 class=3D160261800-07062005></SPAN></FONT></FONT></FONT> </DIV> <DIV><FONT><FONT><FONT face=3DArial size=3D2><SPAN=20 class=3D160261800-07062005>Ugo</SPAN></FONT></FONT></FONT></DIV></BODY></= HTML> ------_=_NextPart_001_01C56AF7.783B32A7--
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]