[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: notes from f2f meeting on Nov. 14
TO (bold text between *** has been inserted)
If the <repeatEvery> expression is specified
with either the <for> or the <until> expression, the first
alarm is not fired until the time specified in the <for> or <until>
expression expires; thereafter it is fired repeatedly at the interval specified
by the <repeatEvery> expression. *** The duration for the <repeatEvery>
is calculated when the parent scope (the scope which directly encloses
the event handler) starts. *** If the specified duration value for
<repeatEvery> is zero or negative then the standard fault bpel:invalidExpressionValue
MUST be thrown.
Passed, applied to spec. substantive.
R31 - Proposal in
Section 10.4:
Change from:
WS-BPEL treats faults based on abstract WSDL 1.1 operation
definitions, without reference to binding details. This limits the ability
of a WS-BPEL process to determine the information transmitted when faults
are returned over a SOAP binding.
Change to:
WS-BPEL treats faults based on abstract WSDL 1.1 operation
definitions. This limits the ability of a WS-BPEL process to determine
the information transmitted when faults are returned, such as for a SOAP
binding (See Section 10.3, Invoking Web Services Operations - Invoke for
fault treatment).
Closed as proposed, applied to spec.
Editorial
R32
Motion to open and close a and b - c
to be treated separately later. Mult instances of b in section 15.2.
Closed and applied to spec. Editorial.
R40
part 1:
Adding the <from/> and <to/>
to the lists
part 2:
Add a paragraph after the literal value
paragraphs (Before para starting In addition to ... )
Empty variant: The sixth from-spec variant and fifth
to-spec variant are included to explicitly show that from-spec and to-spec
are extensible. Note that if these variants are not extended, or the extensions
are not understood, they MUST behave as if they were an expression variant
returning zero nodes.
Passed, applied to spec.
Substantive
R33 - defer to Wed
R27
Add to 12.6 before the last paragraph
that starts " Forced termination of nexted ... "
A fault in a termination handler MUST cause all running
contained activities to be terminated (see also Section 12.4.4.3 Compensation
within FCT-Handlers).
Passed, applied to spec.
Editorial.
R26 - defer to Wed
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]