[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsbpel] Issue - 293 - Assigning from/to partnerLinks requiresadditional static analysis statements
Yes, sounds good.
Best regards/Mit freundlichen Grüßen,
Thomas Schulze
Alex Yiu
<alex.yiu@oracle.
com> To
wsbpel@lists.oasis-open.org
04.06.2006 23:51 cc
Alex Yiu <alex.yiu@oracle.com>
Subject
Re: [wsbpel] Issue - 293 -
Assigning from/to partnerLinks
requires additional static analysis
statements
+1 in general. But, we may want to do some minor english and terminologies
usage.
From:
The value "myRole" means that the endpoint reference of the process
with respect to that partnerLink is the source, while the value
"partnerRole" means that the partner's endpoint reference for the
partnerLink is the source.
To:
The value "myRole" means that the endpoint reference of the process
with respect to that partnerLink is the source, while the value
"partnerRole" means that the partner's endpoint reference for the
partnerLink is the source. If the value "myRole" or "partnerRole" is
used, the corresponding partnerLink declaration MUST specify the
corresponding myRole or partnerRole attribute. This restriction MUST
be statically enforced.
From:
For the to-spec, the assignment is only possible to the partnerRole,
hence there is no need to specify the role.
To:
For the to-spec, the assignment is only possible to the partnerRole,
hence there is no need to specify the role. Therefore, to-spec can
only refer to a partnerLink of which the declaration specifies the
partnerRole attribute. This restriction MUST be statically enforced.
I hope that sounds OK to you guys.
Thanks!
Regards,
Alex Yiu
ws-bpel issues list editor wrote:
This issue has been added to the wsbpel issue list with a status of
"received". The status will be changed to "open" if a motion to open
the issue is proposed and that motion is approved by the TC. A motion
could also be proposed to close it without further consideration.
Otherwise it will remain as "received".
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 version of the document entitled in
the "Issues" folder of the WSBPEL TC document list - the next posting
as a TC document 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.
Issue - 293 - Assigning from/to partnerLinks requires additional
static analysis statements
Status: received
Date added: 4 Jun 2006
Date submitted: 02 June 2006
Submitter: Thomas Schulze
Document: WS-BPEL 2.0 Committee Draft, section 8.4.
Description: Action Item #125 addresses this additional text. Because
this is a normative change AI #125 will be closed and is addressed by
this issue.
There is currently no text which specifies that static analysis have
to catch possible errors when assigning from/to partnerLinks.
Submitter's proposal:
Change/add the following sentences in the PartnerLink variant
paragraph in section 8.4.
From:
The value "myRole" means that the endpoint reference of the
process with respect to that partnerLink is the source, while
the value "partnerRole" means that the partner's endpoint
reference for the partnerLink is the source.
To:
The value "myRole" means that the endpoint reference of the
process with respect to that partnerLink is the source, while
the value "partnerRole" means that the partner's endpoint
reference for the partnerLink is the source. If the value
"myRole" or "partnerRole" is used, the corresponding
partnerLink MUST specify the corresponding myRole or
partnerRole attribute. This restriction MUST be statically
enforced.
From:
For the to-spec, the assignment is only possible to the
partnerRole, hence there is no need to specify the role.
To:
For the to-spec, the assignment is only possible to the
partnerRole, hence there is no need to specify the role.
Therefore, in the to-spec only partnerLinks are permitted which
specify the attribute partnerRole. This restriction MUST be
statically enforced.
Changes: 4 Jun 2006 - new issue
To comment on this issue (including whether it should be accepted),
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 - 293 - [anything]" or is a reply
to such a message. If you want to formally propose a resolution to an
open issue, please start the subject line "Issue - 293 - Proposed
resolution", without any Re: or similar.
To add a new issue, see the issues procedures document (but the
address for new issue submission is the sender of this announcement).
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs in
OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]