Ugo,
I would agree this seems to be a problem
in the schema and an issue should be opened for it. Activities nested within fault handlers and
compensation handlers should allow compensate activities. But as you said the schema doesn’t
allow it.
Regards,
Chris
-----Original Message-----
From: Ugo Corda
[mailto:UCorda@SeeBeyond.com]
Sent: Wednesday, January 28, 2004 5:14 PM
To: wsbpel@lists.oasis-open.org
Subject: RE: [wsbpel]
Clarification: how many activities within a compensation handler or a fault
handler?
Let me be more specific about what I
am asking. I would like to be able to specify a
"compensate" plus other activities. The use of a single
<sequence>, <flow>, etc. would not allow me to do that, because the
set of activities allowed within them excludes "compensate".
-----Original Message-----
From: Ugo Corda
Sent: Wednesday, January 28, 2004
2:00 PM
To: wsbpel@lists.oasis-open.org
Subject: [wsbpel] Clarification:
how many activities within a compensation handler or a fault handler?
The BPEL Schema
indicates that a compensation handler or a catch clause in a fault handler can
only accept a single "activity" (which could in particular be a
compensate).
On the other hand, section 13.3.2 seems to indicate
that multiple activities should be allowed:
"The <compensate/> form, in which the
scope name is omitted in a compensate activity, causes this default behavior to
be invoked explicitly. This is useful when an enclosing fault or compensation
handler needs to perform additional work, such as updating variables or sending
external notifications, in addition to performing default compensation for
inner scopes"
and
"The use of this activity can be mixed with any
other user-specified behavior except the explicit invocation of <compensate
scope="Sx"/> for scope Sx nested directly within S".
Unless I am missing something obvious (in which case
somebody will certainly promptly point that out to me), I'll submit a new Issue
for this.
Ugo