- From: Steve Ross-Talbot <steve@pi4tech.com>
- Date: Tue, 30 Aug 2005 21:16:13 +0100
- To: 'WS-Choreography List' <public-ws-chor@w3.org>
The enclosed fragment is provided to provoke and encourage discussion of the exception binding issue raised some time ago. Charlton's email is at: http://lists.w3.org/Archives/Public/public-ws-chor/2005Aug/0026.html Chair note: 10 min discussion without reaching any conclusion Charlton: I'm working to get my example out by the end of this week, so as to facilitate discussion at next weeks call http://www.w3.org/2002/ws/chor/edcopies/cdl/cdl.html#Interacting Nick: Within the exchange element, the OPTIONAL faultName attribute is used to identify this exchange element as a fault exchange with the specified name. If the faultName attribute is specified, then it will be used to identify the specific fault within the context of the operation. If the operation is defined using WSDL, this will occur in the following way: Nick: In WSDL/CDL faultName always points to fault operation in WSDL. But in BPEL it is associated with a QName only. We could therefore say that the QName coming from anywhere could map to a faultName in CDL. Gary suggests that "causeException="qname"" in the exchange can be used to do this today Binding of the qname to something specific is then a separate binding problem. Comments people ...... Cheers Steve T
Received on Tuesday, 30 August 2005 20:16:23 UTC