Assigned: http://www.osoa.org/jira/browse/BP-49
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: MaxOccurs Constraint Missing in tFrom
Target: ws-humantask.xsd
Description: In WS-HumanTask 1.1, section 3.2.1, the “from” element is defined
with zero or more arguments – the XML Schema definition only has minOccurs=”0”
and the missing maxOccurs attribute implies a default value of 1.
Note that the similar problem does not occur in bpel4people.xsd as the
“argument” is an extension child element of <bpel:from> which already
allows an arbitrary number of extension child elements.
Proposal: In ws-humantask.xsd, add maxOccurs=”unbounded” to the “argument”
element inside the “tFrom” definition as shown below.
<xsd:complexType
name="tFrom"
mixed="true">
<xsd:complexContent>
<xsd:extension base="tExtensibleMixedContentElements">
<xsd:sequence>
<xsd:choice>
<xsd:element
name="argument"
type="tArgument"
minOccurs="0"
maxOccurs="unbounded"
/>
<xsd:element
name="literal"
type="tLiteral"
minOccurs="0"
/>
</xsd:choice>
</xsd:sequence>
<xsd:attribute name="expressionLanguage"
type="xsd:anyURI"
/>
<xsd:attribute name="logicalPeopleGroup"
type="xsd:QName"
/>
</xsd:extension>
</xsd:complexContent>
</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 |
|
|
E-Mail: |
dieterkoenig@de.ibm.com |
Schönaicher Str. 220 |
|
|
71032 Böblingen |
|||
|
Germany |
|||
|
|
|||
|
IBM Deutschland Research & Development GmbH / Vorsitzender
des Aufsichtsrats: Martin Jetter |
|||
