BP-26: Inconvenient Return Type of getFault API Operation

["Luc Clement" <luc.clement@activevos.com>]

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

-----Original Message-----
From: Dieter Koenig1 [mailto:dieterkoenig@de.ibm.com] 
Sent: Friday, October 24, 2008 09:07
To: bpel4people@lists.oasis-open.org
Subject: [bpel4people] NEW ISSUE: Inconvenient Return Type of getFault API
Operation



TARGET: WS-HumanTask 1.1, section 6.1.1 "Participant Operations" and
"ws-humantask-api.wsdl" / "ws-humantask-types.xsd"

DESCRIPTION: The "getFault" operation returns the fault name and the fault
data for a specified task. Consequently, the XML Schema element definition
for the "getFaultResponse" response wrapper element contains two elements
"faultName" and "faultData". Note that the "getFault" operation is the only
operation that does not return a single output element.

While this is still a correct use of document-literal wrapper style (as
defined in JAX-WS 2.0, section 2.3.1.2 "Wrapper Style"), it is inconvenient
for some "WSDL to Java" mapping tools. If a response wrapper contains a
single wrapper child element then this can be mapped to a Java method
return value (see JAX-WS 2.0, section 2.3.2 "Parameter Order and Return
Type").

PROPOSAL: Wrap the two elements into a single child element such that it
can be mapped to a method return value.

A. In WS-HumanTask 1.1, section 6.1.1 "Participant Operations", table entry
"getFault", column "Parameters", paragraph "Out", 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 "getFaultResponse" response
wrapper element definition:

<.xsd:element name="getFaultResponse">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="faultName" type="xsd:NCName" />
      <xsd:element name="faultData" type="xsd:anyType" />
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

by::

<xsd:element name="getFaultResponse">
  <xsd:complexType>
    <xsd:sequence>
      <xsd:element name="fault" type="htt:tFault" />
    </xsd:sequence>
  </xsd:complexType>
</xsd:element>

and add the "tFault" complex type definition to "ws-humantask-types.xsd":

<xsd:complexType name="tFault">
  <xsd:sequence>
    <xsd:element name="faultName" type="xsd:NCName" />
    <xsd:element name="faultData" type="xsd:anyType" />
  </xsd:sequence>
</xsd:complexType>


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
(Embedded 
 
image moved 
 
to file: 
 
pic09415.gif) 
 

 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