[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [wsbpel] Issue - 52 - Proposal For Vote
If one *really* chooses to model a process like this, it can be done
already:
assign-copy from partnerLink "myself-inbound" (myRole) to
"myself-outbound" (partnerRole)
invoke (use partnerLink "myself-outbound" and a correlation set to get
the same instance)
receive (use partnerLink "myself-inbound" and a correlation set to get
the same instance)
In addition, imo, we should not introduce a dedicated construct which
encourages intra-process-instance communication patterns that are asking
for deadlocks.
Kind Regards
DK
"Yaron Y. Goland"
<ygoland@bea.com>
To
16.09.2004 03:05 wsbpeltc
<wsbpel@lists.oasis-open.org>
cc
Please respond to
ygoland Subject
[wsbpel] Issue - 52 - Proposal For
Vote
In section 6.2, 7.2
Change the partnerLink schema to:
<partnerLinks>
<partnerLink name="ncname" partnerLinkType="qname"
myRole="ncname"? partnerRole="ncname"?
partnerIsSelf="Boolean"?>+
</partnerLink>
</partnerLinks>
Add the following text to the end of section 7.2:
If the partnerIsSelf attribute is set to true then it indicates that the
partnerRole points to the BPEL process instance in which the partnerLink
is being used. The default value of the partnerIsSelf attribute is
false. partnerIsSelf is used to support internal communication so that a
BPEL process instance can send messages to itself. By specifying
partnerIsSelf="true" the BPEL engine knows that it is to provide a
binding for the partnerRole that points at the BPEL process instance.
Add the following to the schema definition of tPartnerLink:
<attribute name="partnerIsSelf" type="bpws:tBoolean" use="optional"
default="no"/>
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]