wsrp message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [wsrp-comment] Public Comment
- From: Rich Thompson <richt2@us.ibm.com>
- To: remo.jongeneelen@gmail.com
- Date: Wed, 28 Jun 2006 08:52:46 -0400
Thanks for pointing this out. I think
it is the description that is incorrect as the intent is to indicate that
a set of events all failed to be processed for the same reason.
Rich Thompson
OASIS WSRP TC Chair
IBM T.J. Watson Research Center / Yorktown Heights, NY
comment-form@oasis-open.org
06/28/06 08:15 AM
Please respond to
remo.jongeneelen@gmail.com |
|
To
| wsrp-comment@lists.oasis-open.org
|
cc
|
|
Subject
| [wsrp-comment] Public Comment |
|
Comment from: remo.jongeneelen@gmail.com
Name: Remo Jongeneelen
Title: Freelance .NET developer/arch
Organization: Free IT
Regarding Specification: WSRP v2.0
Section 6.1.21 (HandleEventsFailed Type):
Within the specification PDF, member "index" is defined as an
array of int.
Within the wsrp_v2_types.xsd this element is also specified with maxOccurs
"unbounded".
Both these facts mean that this member can occur more than once.
Yet, the description of this field seems to mention that it will always
contain a single 0-based index. This also matches with the fact that there's
only one errorCode field and only one reason field.
Shouldn't this field simply be of type int with maxOccurs 1?
---------------------------------------------------------------------
To unsubscribe, e-mail: wsrp-comment-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: wsrp-comment-help@lists.oasis-open.org
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]