[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Public Comment
Comment from: cindymcnally_6@hotmail.com the spec doesn't provide much guidance as to how the variable referenced by a throw activity should be managed. variables declared on a catchFault are local to the faultHandler, so the variable referenced by throw activity cannot reference the same actual instance declared by faultHandler. does this mean that the faultHandler must declare a variable of matching type and the bpel implementation must populate the variable with data from this variable ??? this seems awkward at best, as the same can be accomplished by defining a faultHandler with no variable declaration, but that works with throw instance directly, ie. the variable is declared in an enclosing scope that is visible to both throw activity and the faultHandler that catches the fault that is thrown. in my opinion, this feature should be dropped or the explanation and mechanics embellished. Thx.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]