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

 


Help: OASIS Mailing Lists Help | MarkMail Help

bpel4people message

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


Subject: BP-60: Use tFault in setFault and fail API Methods


Assigned: http://www.osoa.org/jira/browse/BP-60

 

From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com]
Sent: Tuesday, December 02, 2008 12:17
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] New Issue: Use tFault in setFault and fail API Methods

 


Target: WS-HumanTask 1.1, ws-humantask-api.wsdl (Follow-up from Issue 46)

Description: In the resolution of Issue 46, the wrapper type tFault (containing a fault name and fault data) was introduced as return value for the getFault() API operation.

The setFault() and fail() operations also use the faultName and faultData elements (as input parameter).

Proposal: Consistently use the tFault wrapper type, that is, replace occurrences of two individual fault-related parameters by one parameter of type tFault.

A: In WS-HumanTask 1.1, section 6.1.1 "Participant Operations", table entry "setFault" and “fail”, column "Parameters", paragraph "In", replace the two bullets "faultName" and "faultData" by a single bullet "fault – contains the fault name and the fault data".

B: In "ws-humantask-api.wsdl", replace the "setFault" and “fail” input wrapper element definitions in order to use the newly created tFault type instead faultName and faultData.

Replace:
<xsd:element name="setFault">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="identifier" type="xsd:anyURI"/>
      <xsd:element name="faultName" type="xsd:NCName"/>
      <xsd:element name="faultData" type="xsd:anyType"/>
    </xsd:sequence>
</xsd:complexType>
</xsd:element>

by:
<xsd:element name="setFault">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="identifier" type="xsd:anyURI"/>
      <xsd:element name="fault" type="htt:tFault"/>
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>
 
Replace:
<xsd:element name="fail">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="identifier" type="xsd:anyURI"/>
      <xsd:element minOccurs="0" name="faultName" type="xsd:NCName"/>
      <xsd:element minOccurs="0" name="faultData" type="xsd:anyType"/>
    </xsd:sequence>
</xsd:complexType>
</xsd:element>

by:
<xsd:element name="fail">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="identifier" type="xsd:anyURI"/>
      <xsd:element minOccurs="0" name="fault" type="htt:tFault" />
    </xsd:sequence>
</xsd:complexType>
</xsd:element>

Kind Regards

Dieter König

Senior Technical Staff Member, WebSphere Process Server Architect
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions


Phone:

+49-7031-16-3426

 IBM Deutschland

E-Mail:

dieterkoenig@de.ibm.com

 Schönaicher Str. 220

 71032 Böblingen

 Germany


IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter
Geschäftsführung: Erich Baier
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294

 



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