Tomohiro,
The decision in SLC was
that a queryConfirmed would be returned with no results for the
connectionID or globalReservationId that did not match. If you send 10
connectionIds in a query request and get only five results, then you can
derive that 5 connectionIds did not match reservations.
The only
time a queryFailed is returned is if there is a true error and never
for a non-match.
John.
Hi John,
We have a question:
If
multiple connection ids are specified in a query message, and one
or
more of them are invalid (non-exist) ids, should the query fail? Or,
just
return an array with null elements?
Thanks,
Tomohiro
On
Mon, 8 Aug 2011 17:47:50 -0400
Peoples,
Here is the latest (and I
hope the last) update to the WSDL.
John.
Version 0.09
Changes to NSI WSDL specification
Date: August 6, 2011
Author:
John MacAuley
1. Changed all occurrences of Requestor to
Requester in the documentation, names, and bindings.
2. Capitalized
enumerated values in DirectionalityType to "Bidirectional" and
"Unidirectional".
3. Set directionality default to "Bidirectional".
4.
Added connectionState to DetailedPathType so each NSA down the tree
will provide its view of the state machine.
5. Modified
ReservationConfirmedType to return only summary reservation information
and not the detailed path.
5. Created new QueryOperationType with
values "Summary" and "Details" to allow modeling of two separate query
operations. The "Summary" operation matches the behavior of our
original query on level deep in the tree, while "Details" performs a
recursive query down the tree to build a complete path view from all
children.
6. Modified the QueryFilterType to use QueryOperationType
allowing the requester to specify if summary or detailed path results
should be returned.
7. Restructured the QueryConfirmedType to support
returning of a choice of summary reservation information or detailed
path results.
8. Created QuerySummaryResultType to hold the query
summary results.
9. Removed DetailedReservationInfoGroup to
QueryDetailsResultType to hold the recursive path query results.
10.
Modified QueryConfirmedType to return a choice of reservationSummary or
reservationDetails.
11. Removed AttributeSequenceType and replaced
with saml:AttributeStatementType to avoid naming conflicts with
AttributeType definition with exists in both namespaces.
12. Removed
SubjectAttributeSequenceType and replaced with equivalent
saml:AttributeStatementType.
---------------