[ http://issues.apache.org/jira/browse/JUDDI-57?page=comments#action_59688 ] Steve Viens commented on JUDDI-57: ----------------------------------
See the juddi-dev archives for more information on this issue: http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=1442 > delete_business | service | binding do not return problem keys in error text > ---------------------------------------------------------------------------- > > Key: JUDDI-57 > URL: http://issues.apache.org/jira/browse/JUDDI-57 > Project: jUDDI > Type: Bug > Versions: 0.9rc3 > Reporter: Steve Viens > Assignee: Steve Viens > Fix For: 0.9 > > Steve Viens: I just checked this out and it's a bug ... and one that's also a > problem for delete_service and delete_binding. > Although the v2 spec doesn't explicitly give you a way to determine the > problem on the client side programmatically". The following seems to say that > a key will exist *someplace* within the error text: > "The key that caused the error will be > clearly indicated in the error text." > Anne Manes: According to the UDDI v2 spec, the SOAP fault should return the > key that was invalid: > E_invalidKeyPassed: signifies that one of the uuid_key values passed did not > match with any known businessKey values. No partial results will be returned > � if any businessKey values passed are not valid or if the message contained > multiple instances of a uuid_key value, this error will be returned. The key > that caused the error will be clearly indicated in the error text. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
