Re: [wsbpel] Issue 247 What goes into the static analysis table?

[Monica J Martin <Monica.Martin@Sun.COM>]

Mark,
In looking at the editors' most recent version of Section 11 (11.6.3), 
Danny vanderRijn pointed out a change that had not been applied related 
to Issue 204.  In that issue a syntactic static analysis requirement 
appears to be referenced. Note, I plan to bring this up in the Section 
11 review so a proposed textual change can be considered. Issue 204 
resolution (from Alex Yiu) references this syntactic restriction and 
static analysis.

11.7 (line 4452):
In order to address Danny's mention of Issue 204.
Change from:
The child activity of a <forEach> MUST be a <scope> activity.  The 
<forEach> construct introduces an implicit counter variable, and also 
introduces dynamic parallelism.

Change from:
The child activity of a <forEach> MUST be a <scope> activity.  This MUST 
be enforced by static analysis. The <forEach> construct introduces an 
implicit counter variable, and also introduces dynamic parallelism (i.e. 
having parallel branches of which number is not known ahead of time).

Reference in Issue 204 resolution:

    "...Recap and More Details:
    To restrict that the child activity of:
    (a) an <onEvent> and <onAlarm> under <eventHandler>
    (b) a <forEach> activity
    MUST be a <scope> activity.

    This restriction MUST be enforced during static analysis. (XSD will
    be updated to reflect this restriction). ..."

    See: http://lists.oasis-open.org/archives/wsbpel/200507/msg00077.html

Thanks.