find_service/find_binding queries constrained by business/service keys do not
return SOAP faults
------------------------------------------------------------------------------------------------
Key: JUDDI-432
URL: https://issues.apache.org/jira/browse/JUDDI-432
Project: jUDDI
Issue Type: Bug
Components: core
Affects Versions: 3.0.3
Environment: Tomcat 6.0.24 PostgreSQL 8.4
Reporter: Jason Brown
Assignee: Kurt T Stam
Priority: Minor
In the case where a find_service/find_binding query is constrained by a
businessKey/serviceKey and the key does not exist as follows (assume all other
keys exist in the registry):
<find_binding xmlns="urn:uddi-org:api_v3" serviceKey="uddi:keydoesnotexist">
<categoryBag>
<keyedReference tModelKey="uddi:testkey"
keyValue="testvalue"/>
</categoryBag>
</find_binding>
<find_service xmlns="urn:uddi-org:api_v3" businessKey="uddi:keydoesnotexist">
<name>testname</name>
</find_service>
jUDDI returns an empty list description. It is implied in the spec, and has
been seen in other implementations, that perhaps a SOAP fault should be
returned with an E_InvalidKeyPassed (see section 5.1.12.4 and section 5.1.9.4
of the UDDI v3 spec, which seem to indicate an E_InvalidKeyPassed SOAP Fault
would be returned in the event of a value passed that did not match a known
business/service key).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
