[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue - 166 - Proposal To Vote
Hello, an assign-specifying appendix sounds usefull to me. There are some points, which are not really addressed. For example is the assign schema aware? If I have a "a (b,c)" complex type and assign <from>C</from><to query="/a/c" /> <from>B</from><to query="/a/b" /> A non schema aware assign implementation may result in <a><c>C</c><b>B</b></a>. Also the question if <to query="/a[2]/c"> is an valid XPath expression should be addresed here. Generally I think this section has to be written after we have clearly defined what will be the required set of capabilities a native BPEL data mangling functions need to have. Currently I can be standard compliant even in some looped processing contexts, using []-index (and $-variables) without missing insert/append too much. Mit freundlichen Grüßen Bernd Eckenfels Chief Architect -- SEEBURGER AG - Edisonstr.1 , D-75015 Bretten, Germany Fax: +49 (0)7252 96-2400 - Phone: +49 (0)7252 96-1256 mailto:b.eckenfels@seeburger.de - http://www.seeburger.de -----Original Message----- From: andrew.francis@mail.mcgill.ca [mailto:andrew.francis@mail.mcgill.ca] Sent: Tuesday, October 19, 2004 2:16 AM To: dannyv@tibco.com Cc: andrew.francis@mail.mcgill.ca; wsbpel@lists.oasis-open.org Subject: Re: [wsbpel] Issue - 166 - Proposal To Vote Hello Danny: > it would be incorrect to state that assign has ACID > properties - neither Consistency nor Durability is mentioned > here. and i think that the conflation of Atomic > with ACID is what got us to the point of > discussing Isolation in the first place. I originally felt that the current wording of section 14.3 was good enough. However I realised that one needs more, i.e., isolation. The question is would stating that assign has ACID properties give the typical programmer the behaviour they expect? At this stage, all I can say is that the committee should decide on the type of behaviour the typical BPEL programmer would expect. After all, the programmers are the customers. And craft section 14.3's wording appropriately. Due the importance and technical nature of 14.3, again I would state that an appendix is added that states in a more formal, precise language, exactly what is assign's behaviour. This more formal (but not too formal) specification is for the BPEL engine designer and computer scientist. Cheers, Andrew > > andrew.francis@mail.mcgill.ca wrote: > > Hello Danny: > > > > "The assign activity MUST be atomic, that is either > all > <copy> elements are performed, or none are. > > > > I have two suggestions. The first is to state that > assign exhibits ACID properties. This is the natural > language narrative. Secondly, write an appendix, which > in a more formal language, describes the behaviour of > assign. This way we get rid of the ambiguity for the > BPEL engine designer. > > Cheers, > Andrew > > > > To unsubscribe from this mailing list (and be removed > from the roster of the OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.> > > > > > > > To unsubscribe from this mailing list (and be removed > from the roster of the OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php. To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]