[ 
https://issues.apache.org/jira/browse/JUDDI-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690991#comment-16690991
 ] 

ASF subversion and git services commented on JUDDI-992:
-------------------------------------------------------

Commit 2f5a2492e49a64da73e29bc5ba0a8bf151b49bdb in juddi's branch 
refs/heads/master from [~spyhunter99]
[ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=2f5a249 ]

JUDDI-992 fix for several issues with find binding with and without the service 
key. Also had to do some light refactoring of List<?> to List<Object> for many 
of the apis in juddi-core. Shouldn't effect too many users.


> FindBinding API call doesn't exactly match the spec
> ---------------------------------------------------
>
>                 Key: JUDDI-992
>                 URL: https://issues.apache.org/jira/browse/JUDDI-992
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>            Reporter: Alex O'Ree
>            Priority: Major
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to