[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Issue - 117 - Link Name Scoping
This issue has been added to the wsbpel issue list. The issues list is posted as a Technical Committee document to the OASIS WSBPEL TC pages on a regular basis. The current edition, as a TC document, is the most recent document with the title in the "Issues" folder of the WSBPEL TC document list - the next posting will include this issue. The list editor's working copy, which will normally include an issue when it is announced, is available at this constant URL.
Discussion:
Suppose we have the following process:
<flow name="F1"> <links> <link name="L1"/> <!-- L1 is defined here and ... --> </links> <sequence name="S1"> <flow name="F2"> <links> <link name="L1"/> <!-- ... here --> </links> <sequence name="S2"> <invoke name="I1" ...> <target linkName="L1"/> <!-- Which L1? --> </invoke> ...
Note that link L1 is defined at two places.
Q1: Is this definition legal?
Q2: If legal, is I1 target of L1 of F2 (F2.L1)
or L1 of F1 (F1.L1)?
Submitter's proposal: Allow defining links with the same name. For a referencing activity, the inner-most link
for the activity hides all other links with the same name. (In the above example,
activity I1 is the target of link F2.L1, not F1.L1.)
Links: Yuzo Fujishima, 13 Apr 2004
rkhalaf, 13 Apr 2004
Yaron Y. Goland, 13 Apr 2004
Changes: 14 Apr 2004 - new issue
To comment on this issue, please follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying to this message should automatically send your message to that list), or ensure the subject line as you send it starts "Issue - 117 - [anything]" or is a reply to such a message.
To add a new issue, see the issues procedures document (but the address for new issue submission is the sender of this announcement).
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]