[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsbpel] Issue 252 - proposal for vote
How does your proposal affect the existing fault:
bpel:forEachCounterError? The spec currently has this fault thrown during the
evaluation of the forEach's start and final counter values. It makes no mention
of the completion condition expression.
From: Alex Yiu
[mailto:alex.yiu@oracle.com]
Sent: Friday, March 31, 2006 10:34 AM To: Alex Yiu Cc: wsbpeltc; 'Dieter Koenig1'; Simon D Moser; Danny van der Rijn Subject: [wsbpel] Issue 252 - proposal for vote Hi all, This is the *formal* proposal for *vote*. The proposal is virtually the same compared with my last email with some minor supplement texts are added at the end. In Section "8.3. Expressions" After this paragraph: ------------------------------- WS-BPEL uses several types of expressions, as follows (relevant usage contexts are listed in parentheses):
Add the following paragraph: ------------------------------- When the above first four types of expressions are being used, the corresponding expressions SHOULD return values which are valid according to the corresponding XML Schema types:
The following values conversion and validity checking semantics MUST be applied when WS-BPEL's default binding to XPath 1.0 ("urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0") is used as the expression language:
Add the following fault description to Appendix A: ------------------------------- invalidExpressionValue fault throw when an expression used within a WS-BPEL construct (non-<assign> construct) returns an invalid value (for example, the branches expression within <forEach> returns -1) ------------------------------- Thanks! Regards, Alex Yiu |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]