wsbpel message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: issue 9 - resolution passed on Mar 15 call
- From: Diane Jordan <drj@us.ibm.com>
- To: wsbpel@lists.oasis-open.org
- Date: Wed, 15 Mar 2006 12:41:04 -0500
This is the final text approved
for the resolution to issue 9:
WS-BPEL takes it as a general principle
that conformant implementations MUST perform basic static analysis listed
in Appendix [TBD - xref to Issue 84] to detect and reject process definitions
that fail any of those static analysis check. Please note that such analysis
might in some cases prevent the use of processes that would not, in fact,
create situations with errors, either in specific uses or in any use. For
example, a WS-BPEL implementation will reject a process with <invoke>
activity referring to an undefined variable, where the <invoke> activity
may not be actually reached during execution of the process.
A WS-BPEL implementation MAY perform
extra static analysis checking beyond the basic static analysis required
by this specification to signal warnings or even reject process definitions.
Such an implementation SHOULD be configurable to disable these non-specified
static analysis checks.
Note: editors should verify the
example used actually appears in the appendix.
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]