Subject: RE: [wsbpel] Issue 163 - Proposal For Vote
If we can’t come up with a schema for the fault data then I wonder how useful such a fault would be – it would then fall in the category of “infrastructure faults” which we cannot usefully specify. S.
From: Danny van der Rijn [mailto:firstname.lastname@example.org]
I lost this issue in the shuffle somehow. Thanks
to Yaron for being on the other side of the whip. Please accept my
submitted proposal as such (deleting/ignoring the question).
Now submitted as 163, with status "received".
It is presumably open to the TC to accept this as a bug, treat Danny's
solution as a proposed resolution to the then open issue, and agree the
resolution in a matter of 5 minutes, since the f-t-f is quorate.
-----Original Message-----From: Danny van der Rijn [mailto:email@example.com]Sent: 22 September 2004 01:52To: Furniss, PeterSubject: New Issue: languageExecutionFault (comes withproposal to vote)This issue came up during our F2F discussion of issue 89 today. Notethat I sent it to Peter as per our process, so that it canget assignedan issue number. However, it was mentioned today that wemight want toaccept it and deal with it during our meeting tomorrow, soPeter may nothave dealt with it yet. So I am cc-ing the list in casePeter's processdoesn't assign it a number and resend to the list by the timewe want todeal with it. I imagine that it would probably aid theissues list ifany email discussion on it were held off until the issue number wereassigned.Discussion: If a language that is executing subordinate toBPEL (e.g.XPATH) throws a fault, there is no current spec language that defineswhat to do with it. This proposal clarifies that behavior.Proposal: To add a new standard fault,languageExecutionFault, which isthrown if the expression language or xxx throws an unhandled fault.Add to the end of section 14.1 "If execution of theexpression languageyields an unhandled fault, the standard faultlanguageExecutionFault isthrown.Add to the end of section 14.3 "If execution of the query languageyields an unhandled fault, the standard faultlanguageExecutionFault isthrown.Question: Should this fault define a message type (or shoulda genericmessage type be defined) to carry any additional data that isreceivedfrom the executing language?