[ http://wso2.org/jira/browse/MASHUP-435?page=all ]
Keith Godwin Chapman resolved MASHUP-435.
-----------------------------------------
Resolution: Fixed
> rpc:signature extension doesn't preserve annotation order.
> ----------------------------------------------------------
>
> Key: MASHUP-435
> URL: http://wso2.org/jira/browse/MASHUP-435
> Project: WSO2 Mashup Server
> Issue Type: Bug
> Reporter: Jonathan Marsh
> Assigned To: Keith Godwin Chapman
>
> Accessing /services/wso2builds?wsdl2 shows the namedBuild:
> wrpc:signature="includeDetails #in name #in return #out "
> The funciton signature generating this signature is:
> namedBuild.inputTypes = {"name" : "mashup | wso2esb | wso2wsas |
> wso2wsf", "includeDetails" : "boolean"};
> namedBuild.outputType="any";
> function namedBuild(name, includeDetails) {
> Because the rpc:signature doesn't preserve the order, the stub signature
> becomes:
> function namedBuild(includeDetails, name) {}
> This reversal of order is confusing when the author is working on both sides
> (e.g. a custom UI), and in fact shows that the rpc:signature doesn't
> correspond to the original function signature.
> The wso2builds sample is failing because of this (in IE - Firefox has other
> issues.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Mashup-dev mailing list
[email protected]
http://www.wso2.org/cgi-bin/mailman/listinfo/mashup-dev
