[JUDDI-992] FindBinding API call doesn't exactly match the spec, can't search for just the service key

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.6
• Component/s: core
• Assignee: Alex O'Ree
• Reporter: Alex O'Ree
• Created: 17/Nov/18 21:19
• Updated: 05/Dec/18 15:05
• Resolved: 24/Nov/18 15:10

Description

this appears to affect most versions starting with 3.1.5 and newer

The spec isn't exactly clear on what the expected behavior is supposed to be in the case when nothing is specified except for the service key in a findBinding api call. The most logical thing is to return all bindings for that service. The current version of juddi throws an exception stating that it is not a valid request. According to the spec, it looks like it is. The spec actually doesn't really specify what isn't valid except for conflicting find qualifiers

 

Example XML request that fits this profile

 

<find_binding xmlns="urn:uddi-org:api_v3" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#" maxRows="10" serviceKey="uddi:juddi.apache.org:4ff68cf9-0463-45c4-bb9e-5a12f321a9c1"><findQualifiers><findQualifier>sortByNameAsc</findQualifier><findQualifier>approximateMatch</findQualifier></findQualifiers></find_binding>

 

This was discovered in trying to bring Apache Scout up to current jUDDI API levels and debugging unit test failures against 3.3.5.

Issue Links

• causes: SCOUT-134 Scout runs integration tests against a very old version of jUDDI, running against the current causes compile errors and unit test failures
• causes: SCOUT-136 Scout adds sort by name desc to findBinding UDDI requests, which is invalid