wsbpel message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: notes from Nov 15 meeting
- From: Diane Jordan <drj@us.ibm.com>
- To: wsbpel@lists.oasis-open.org
- Date: Wed, 15 Nov 2006 20:54:52 -0500
R26
closed - see
http://www.oasis-open.org/apps/org/workgroup/wsbpel/email/archives/200611/msg00078.html
Substantive
R29
Resolved with
motion to keep the the attribute, remove explanatory
text and add sentance that if the attribute is not specified, partner role
may be initialized by a ws-bpel processor.
substantive
R33
opened
closed with this proposal:
in 5.2 - add attribute to syntax
in 8.4 - add to syntax
in 8.4 - add para on ignoreMissingFromData
attribute
The optional ignoreMissingFromData attribute of the
<copy> construct is used to specify whether a bpel:selectionFailure
standard fault is suppressed as specified in section 8.4.1. Selection Result
of Copy Operations. The default value of the ignoreMissingFromData is "no".
in 8.4.1 - revise paragraph
The <copy> operation is a one-to-one replacement
operation. If the optional ignoreMissingFromData attribute has the value
of "yes" and the from-spec returns zero XML information items
then the <copy> MUST be a "no-op"; no bpel:selectionFailure
is thrown. In this case, the to-spec MUST not be evaluated. A bpel:selectionFailure
MUST still be thrown in the following cases, even if the ignoreMissingFromData
attribute has the value of "yes":
1.the from-spec selects multiple XML information items
2.the from-spec selects one XML information item and the to-spec does not
select exactly one XML information item
If the ignoreMissingFromData attribute has the value of "no"
this requires that both the from-spec and to-spec MUST select exactly one
of the three information items described above. If the from-spec or to-spec
do not select exactly one information item during execution, then the standard
fault bpel:selectionFailure MUST be thrown. The following table illustrates
the behavior of the ignoreMissingFromData attribute in the <copy>
operation:
Appendix e - schema for executable
and abstract
substantive
R25
In 10.4
to: If during the execution of a business process
instance, two or more receive activity instances for the same partnerLink,
operation and correlationSet(s) are simultaneously enabled, then the standard
fault bpel:conflictingReceive MUST be thrown (note bpel:conflictingReceive
differs from bpel:conflictingRequest, see
section 10.4.1. Message Exchanges).
There may be receive activity instances on an operation
where the partnerLink and correlationSet(s) are different, yet indistinguishable
to a WS-BPEL processor at runtime. In these cases, a WS-BPEL processor
SHOULD throw a bpel:conflictingReceive fault.
closed and applied to the spec.
Substantive
Regards, Diane
IBM Emerging Internet Software Standards
drj@us.ibm.com
(919)254-7221 or 8-444-7221, Mobile: 919-624-5123, Fax 845-491-5709
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]