[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Updating htt:tTask in PRD-03 with htt:tTaskDetails
During
the course of work, Mark Ford identified the following issue … do you
know what the following API elements should be
referring to instead of htt:tTask? I'm guessing that htt:tTask was from an
older version of the schema and was renamed to something else. These elements
are from ws-humantask-api.wsdl.
<xsd:element name="getParentTaskResponse"> <xsd:complexType>
<xsd:sequence>
<xsd:element name="parentTask" type="htt:tTask"
minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="getSubtasksResponse">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="subtask" type="htt:tTask"
minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element> Dieter reviewed this and provided the
following in return. However, Mark
Ford discovered an error in the API WSDL. The type of the return value of
the two operations is wrong because it is not defined in the data types
XML Schema (prefix htt). As a consistency issue between WSDL and XSD, this
was not recognized by the XML Schema validations. Just from the WSDL point
of view, it could be handled as an editorial fix and done immediately
(change "htt:tTask" to "htt:tTaskDetails" in these two
places), but there is
also a remark in the API definition table in 7.1.1 that needs to be changed
(for the getSubtasks operation, change "Returns all sub tasks of a task
(created instances + not yet created sub task definitions)") to "Returns
all sub tasks of a task (created instances)". I
propose that we accept Dieters issue. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]