RE: [wsbpel] Outgoing link from a fault handler

["Chris Keller" <chris.keller@active-endpoints.com>]

Hi Yuzo,

E to H should be allowed. If the text is not clear we should change the
sentence to:

  In addition, a link that crosses a fault-handler boundary 
  MUST be outbound, that is, it MUST have its source activity 
  within the fault handler and its target activity MUST not be 
  to an activity within the fault handlers associated scope.

If you think the text is not clear then it probably isn't so I think you
should open an issue?

- Chris
 
-----Original Message-----
From: Yuzo Fujishima [mailto:fujishima@bc.jp.nec.com] 
Sent: Thursday, October 20, 2005 1:56 AM
To: ws bpel tc
Subject: [wsbpel] Outgoing link from a fault handler

Hi,

Could someone help me understand a restriction on link?

In the last paragraph of "12.6 Flow", 
  In addition, a link that crosses a fault-handler boundary 
  MUST be outbound, that is, it MUST have its source activity 
  within the fault handler and its target activity within a 
  scope that encloses the scope associated with the fault handler. 

What is the rationale behind the line above?

Example:

Scope A
  Sequence
    Scope B
      Sequence
        Scope C
          FaultHandler D
            Activity E
        Activity F
    Scope G
      Activity H
    Activity I

As far as I understand the specification,
Link from E:
  to F: Allowed, because B encloses C
  to H: Disallowed, because G does not enclose C.
  to I: Allowed, because A encloses C, although indirectly via B.

I don't quite understand why we should allow/disallow linking as above.

Some may claim:
  E to H is allowed, because it is within A, because it is WITHIN A,
  although indirectly.

One of the problems is, IMHO, the definition of "WITHIN A SCOPE" is unclear.

Yuzo Fujishima
NEC Corporation

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php