[
https://issues.apache.org/jira/browse/SCOUT-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219232#comment-13219232
]
Kurt T Stam commented on SCOUT-129:
-----------------------------------
Additionally UDDIv3 is not happy to have an empty Bag. So if empty we should
set it to null to avoid validation errors for UDDIv3.
> Querying using 'specifications' is not implemented correctly.
> -------------------------------------------------------------
>
> Key: SCOUT-129
> URL: https://issues.apache.org/jira/browse/SCOUT-129
> Project: Scout
> Issue Type: Bug
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 1.2.6
>
>
> The spec seems vague on this:
> findServiceBindings(Key serviceKey, java.util.Collection findQualifiers,
> java.util.Collection classifications, java.util.Collection specifications)
> Finds all ServiceBindings that match ALL of the criteria specified by the
> parameters of this call.
> and
> specifications - a Collection of RegistryObjects that represent (proxy) a
> technical specification. It is analogous to a tModelBag in UDDI. Unless
> otherwise specified in findQualifiers, this is a logical AND and requires a
> match on ALL specified Specifications to qualify as a match for this criteria.
> and the specs' javadoc seems to suggest it should be a concept
> specifications - a Collection of RegistryObjects that represent (proxy) a
> technical specification. It is analogous to a tModelBag in the UDDI
> specification. In the case of a UDDI provider, the RegistryObject is a
> specification Concept. In the case of an ebXML provider, the RegistryObject
> is likely to be an ExtrinsicObject. Unless otherwise specified in
> findQualifiers, this is a logical AND, and a match on all specified
> Specifications qualifies as a match for this criterion.
> Scout currently assumes it contains a list of SpecificationLink, however the
> TCK fails with this, when a Concept is used it passes.
> I"m checking this change in for UDDIv3, and will also make sure the TCK is
> happy with a similar change for UDDIv2 before check in a chnage there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
