juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kurt T Stam (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Updated] (JUDDI-498) Success messages for deletes are not empty
Date Mon, 13 Jun 2011 18:46:57 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kurt T Stam updated JUDDI-498:

    Fix Version/s: 3.1.1

That is right. The method signatures where checked in as part of juddi-276, but seem unrelated
to that fix. Thanks Jason, we will fix it.

> Success messages for deletes are not empty
> ------------------------------------------
>                 Key: JUDDI-498
>                 URL: https://issues.apache.org/jira/browse/JUDDI-498
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.0.4
>         Environment: Tomcat 6.0.24, PostgreSQL 8.4
>            Reporter: Jason Brown
>            Assignee: Kurt T Stam
>             Fix For: 3.1.1
> When deleting an entity in uddi the return should be an empty message " Returns:
Upon successful completion, an empty message is returned." When we are deleting items we are
getting a message back with a disposition report, which should not be the case as a spec compliant
client may not be able to parse that return with the disposition report in place.It appears
that the WSDL jUDDI uses for publication is different from the UDDI v3 port type WSDL.
> jUDDI WSDL - delete_business
> <wsdl:operation name="delete_business"><wsdl:input message="tns:delete_business"
>     </wsdl:input><wsdl:output message="tns:delete_businessResponse" name="delete_businessResponse">
>     </wsdl:output>
> </wsdl:operation>
> UDDI v3 WSDL delete_business
> <operation name="delete_business">
> 			<input message="tns:delete_businessMessage"/>
> 			<output message="tns:successMessage"/>
> 			<fault name="error" message="tns:dispositionReportFaultMessage"/>
> 		</operation>

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message