[
https://wso2.org/jira/browse/MASHUP-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473#action_16473
]
Keith Godwin Chapman commented on MASHUP-781:
---------------------------------------------
Fixed in revision 16490. We had a WebServiceError object from the inception but
its constructor did not match the one in the WSRequest native js. Fixed the
constructor and also renamed details to detail cause this is the one used in
the native JS.
> Stub requires WebServiceError (defined in WSRequest.js but not in the
> WSRequest host object).
> ---------------------------------------------------------------------------------------------
>
> Key: MASHUP-781
> URL: https://wso2.org/jira/browse/MASHUP-781
> Project: WSO2 Mashup Server
> Issue Type: Bug
> Reporter: Jonathan Marsh
> Assignee: Keith Godwin Chapman
> Fix For: 1.1
>
>
> The stub utilizes WebServiceError from WSRequest.js to structure fault
> information. When the stub is imported into a mashup, and a call fails, it
> tries to populate WebServiceError and throws a fault. Can we add such an
> object, or is there a better way I can handle structured fault information in
> the stubs?
> var WebServiceError = function (reason, detail, code) {
> this.reason = reason;
> this.detail = detail;
> this.code = code;
> this.toString = function() { return this.reason; };
> };
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://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
