OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel-spec-edit message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [wsbpel-spec-edit] Proposed text for issue 170 (RESEND)

I am still unsure of what was the original issue in the call that motivated
this discussion but I agree with your statement below. IMO BPEL cannot
access anything but content of the soap:detail field in a fault that is
generated when the body is processed, and in fact only when that that
detail field is associated with a wsdl:fault message in the corresponding
operation (BP10 allows faults other than those indicated by wsdl:fault but
I don't think they fit in BPEL since all reply messages need to be
associated with a wsld operation). As for wsdl specified headers and
associated header faults, the resolution of issue 77 implies that we
consider those headers invisible at the BPEL level (I understand that is
the current situation), so the case in which the fault detail is not used
(because the details go in a header, possibly with a different element) is
something out of scope for BPEL.


|         |           "Satish Thatte"  |
|         |           <satisht@microsof|
|         |           t.com>           |
|         |                            |
|         |           01/14/2005 01:07 |
|         |           PM               |
  |                                                                                                                                     |
  |       To:       Francisco Curbera/Watson/IBM@IBMUS                                                                                  |
  |       cc:       "Liu, Kevin" <kevin.liu@sap.com>, "Kartha, Neelakantan" <N_Kartha@stercomm.com>, "bpel spec"                        |
  |        <wsbpel-spec-edit@lists.oasis-open.org>                                                                                      |
  |       Subject:  RE: [wsbpel-spec-edit] Proposed text for issue 170 (RESEND)                                                         |

So what is your overall recommendation for this issue?  It seems that
you agree BPEL cannot have access to faultcode etc.  Then a BPEL fault
can propagate its fault data only inside the detail element.  Is that

-----Original Message-----
From: Francisco Curbera [mailto:curbera@us.ibm.com]
Sent: Friday, January 14, 2005 7:58 AM
To: Satish Thatte
Cc: Liu, Kevin; Kartha, Neelakantan; bpel spec
Subject: RE: [wsbpel-spec-edit] Proposed text for issue 170 (RESEND)

This is my interpretation of this problem as I understand it (since I
missed the editors call this week I am not sure I have the complete
of the discussion). I hope it helps.


The wsdl:fault message only describes contents of the Detail element in
fault; however, the Detail element cannot be used for header-generated
faults; in that case the soap:fault that is generated goes in the body
contains no soap:detail element. The detail information is included in
header specified by the wsdl-soap:headerfault element, if present. The
element that specifies this information is determined by the message
definition named by the wsdl-soap:headerfault element. BP 1.0 also
detail to be provided when the wsdl description does not specify it (in
wsdl-soap:fault or wsdl-soap:headerfault binding element).

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]