It was agreed at the 12 Nov call (see
http://www.oasis-open.org/apps/org/workgroup/wsbpel/download.php/4283/Mi
nutes%20of%20Conference%20Call%20November%2012%20.doc) to pause issue 2,
pending resolving the coordination/business transaction issues (30,
53-59, ..), on the grounds that the requirement driving issue 2 could
potentially be met by making the content of the "subfunction" a separate
process, using regular invoke and a local binding (the latter invisible
to the bpel scripts). But in that case there is a need to tie the fault
and compensation/cancellation of the parent and child process together -
hence the link to the coordination issues.
As volunteered during that call, Satish is working on a proposal to be
discussed at the face-to-face, with assistance from others.
Peter
> -----Original Message-----
> From: Yaron Goland [mailto:]
> Sent: 25 November 2003 21:17
> To: 'Trickovic, Ivana'; 'Eckenfels. Bernd'
> Cc:
> Subject: [wsbpel] Issue - 2- Why I think we should close Issue 2
>
>
> Over the last two months I have made a series of proposals
> for how to introduce sub-functions to BPEL:
>
> * http://lists.oasis-open.org/archives/wsbpel/200310/msg00355.html
> * http://lists.oasis-open.org/archives/wsbpel/200310/msg00366.html
> * http://lists.oasis-open.org/archives/wsbpel/200310/msg00367.html
> * http://lists.oasis-open.org/archives/wsbpel/200310/msg00368.html
> * http://lists.oasis-open.org/archives/wsbpel/200311/msg00021.html
> * http://lists.oasis-open.org/archives/wsbpel/200311/msg00023.html
>
> Having spent this time living with these proposals I have
> come to the conclusion that it will take us a significant
> amount of time to get everything right and ready for
> implementers to implement.
>
> My personal belief is that customers will benefit more by
> getting the BPEL spec out as early as possible than by having
> sub-functions in the first version of BPEL. Sub-functions are
> something that we can safely add in later as an extension and
> I would certainly expect them to be part of the next version of BPEL.
>
> Therefore I propose that we close Issue 2 with a note that
> the matter should be considered by those working on future
> versions of BPEL.
>
> Yaron
>
>
> 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/le
ave_workgroup.php.
