[JUDDI-432] find_service/find_binding queries constrained by business/service keys do not return SOAP faults

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.3
• Fix Version/s: 3.1.0
• Component/s: core
• Environment: Tomcat 6.0.24 PostgreSQL 8.4
• Assignee: Thomas Cunningham
• Reporter: Jennifer Brown
• Created: 18/Nov/10 17:05
• Updated: 22/Dec/10 18:07
• Resolved: 22/Dec/10 18:06

Description

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).