bpel4people message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Newly Discovered BPEL4People Defect
- From: Dave Ings <ings@ca.ibm.com>
- To: bpel4people@lists.oasis-open.org
- Date: Wed, 9 Jun 2010 10:50:47 -0400
Hi folks,
Earlier this week a new defect was discovered by Mark Ford. We'll need to discuss how (if) we want to address it at today's TC, prior to any CS vote.
Regards, Dave Ings,
Emerging Software Standards
Email: ings@ca.ibm.com
Yahoo Messenger: dave_ings
----- Forwarded by Dave Ings/Toronto/IBM on 2010/06/09 10:48 AM -----
From: Dieter Koenig1 <dieterkoenig@de.ibm.com>
To: Luc Clément <luc.clement@activevos.com>
Cc: Dave Ings/Toronto/IBM@IBMCA, Gerhard Pfau <GPFAU@de.ibm.com>, Matthias Kloppmann <Matthias.Kloppmann@de.ibm.com>
Date: 2010/06/08 11:54 AM
Subject: Re: FW: htt:tTask
Hi Luc, I am not concerned about the non-normative text in 5.1 -- it is ok
to say that the lean task definition is "conceptually derived" from the
standard task definition, even though this is not true for their XML Schema
types (both are derived from a common abstract base type).
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)".
Formally, the TC cannot accept this point (not subject of the 3rd Public
Review), so the remaining process towards an OASIS standard is not
affected. However, we should at least discuss if the above can be handled
an acceptable editorial fix.
Kind Regards
Dieter Koenig
Senior Technical Staff Member, WebSphere BPM Architecture, Standardization,
Integration Quality Assurance
IBM Software Group, Application and Integration Middleware Software
WSS Business Process Solutions
Phone: +49-7031-16-3426 IBM Deutschland (Embedded
image moved
to file:
pic27276.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:
Dirk Wittkopp
Sitz der
Gesellschaft:
Böblingen /
Registergericht:
Amtsgericht
Stuttgart, HRB
243294
From: Luc Clément <luc.clement@activevos.com>
To: "Dave Ings (ings@ca.ibm.com)" <ings@ca.ibm.com>, Dieter
Koenig1/Germany/IBM@IBMDE
Date: 07.06.2010 19:49
Subject: FW: htt:tTask
I started looking at this and there are inconsistencies in 5.1, we refer to
htd:tTask elsewhere htt:tTask… what did we expect?
From: Ford, Mark - 0661 - MITLL [mailto:mark.ford@ll.mit.edu]
Sent: Monday, June 07, 2010 13:06
To: Luc Clément
Subject: htt:tTask
Probably too late to fix but 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>
--
Mark Ford
MIT Lincoln Laboratory
244 Wood Street
Lexington MA 02420
(781) 981-1843
[attachment "pic27276.gif" deleted by Dave Ings/Toronto/IBM]
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]