132753 - nsIException ignored in script invoked from SOAP callback handler.

Status: VERIFIED DUPLICATE of bug 132713

(Core :: XPConnect, defect)

Description

[Ray Whitmer]

The SOAP module has implemented nsIException to give better diagnostic errors to
a javascript developer.  These work great in the normal script.  But if the
script is invoked from the SOAP response listener callback, then instead of
generating the message, it says that the component threw a native object that
was not an exception.

My test case was soapisprimeproxy.js, which is invoked every time you press a
key in the text field of soapisprimenumber.html (both of these located in
mozilla/extensions/xmlextras/tests).

If you edit line 22 of soapisprimeproxy.js and change "boolean" to "float", this
causes an error, because the service returns a boolean (when you press a key in
the text field as described above).  But instead of the correct message related
to xsi:type, you get the message about throwing an object that was not an exception.

jband was able to quickly identify the problem, and I have verified that it
works and makes the error be correctly reported.

Comment 1

[Ray Whitmer]

Attachment: Patch by jband that I tested and does fix the problem.

This patch seems obvious, direct, and would save would-be SOAP developers a
fair amount of hassle.	In my opinion, if we cannot land this for Mozilla 1.0,
then we should have a note in the release notes telling developers how to
convert their calls to synchronous calls to see the real error message whenever
they get this bogus message about throwing a non-exception.

Comment 2

[Ray Whitmer]

In the time it took me to get a good build to get a good build -- a couple of
failed pulls -- to test the fix, another bug was entered on this, which has more
info.

*** This bug has been marked as a duplicate of 132713 ***

Comment 3

[Phil Schwartau]

Verified Duplicate -