You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Jason Brown (JIRA)" <ju...@ws.apache.org> on 2010/11/18 18:06:15 UTC
[jira] Created: (JUDDI-432) find_service/find_binding queries
constrained by business/service keys do not return SOAP faults
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.
[jira] Updated: (JUDDI-432) find_service/find_binding queries
constrained by business/service keys do not return SOAP faults
Posted by "Kurt T Stam (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kurt T Stam updated JUDDI-432:
------------------------------
Fix Version/s: 3.0.5
> 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
> Fix For: 3.0.5
>
>
> 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.
[jira] Assigned: (JUDDI-432) find_service/find_binding queries
constrained by business/service keys do not return SOAP faults
Posted by "Tom Cunningham (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham reassigned JUDDI-432:
------------------------------------
Assignee: Tom Cunningham (was: Kurt T Stam)
> 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: Tom Cunningham
> Priority: Minor
> Fix For: 3.0.5
>
>
> 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.
[jira] Closed: (JUDDI-432) find_service/find_binding queries
constrained by business/service keys do not return SOAP faults
Posted by "Tom Cunningham (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham closed JUDDI-432.
--------------------------------
> 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: Tom Cunningham
> Priority: Minor
> Fix For: 3.0.5
>
>
> 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.
[jira] Resolved: (JUDDI-432) find_service/find_binding queries
constrained by business/service keys do not return SOAP faults
Posted by "Tom Cunningham (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Cunningham resolved JUDDI-432.
----------------------------------
Resolution: Fixed
If we get no results back, and if the businessKey/serviceKey is not null, then check to see if the businessKey/serviceKey actually exists. If it doesn't, throw an E_InvalidKeyPassed (spelled out in sections 5.1.12.4and 5.1.9.4).
Changes here were made to FindBinding and FindService.
> 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: Tom Cunningham
> Priority: Minor
> Fix For: 3.0.5
>
>
> 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.
[jira] Commented: (JUDDI-432) find_service/find_binding queries
constrained by business/service keys do not return SOAP faults
Posted by "Tom Cunningham (JIRA)" <ju...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/JUDDI-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972202#action_12972202 ]
Tom Cunningham commented on JUDDI-432:
--------------------------------------
Grabbing this one from Kurt, he said something might be missing from the validateXXX methods.
> 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: Tom Cunningham
> Priority: Minor
> Fix For: 3.0.5
>
>
> 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.