I propose we change:
/* Default top level exception handler */
JSONRpcClient.default_ex_handler = function (e)
{
alert(e);
};
to
/* Default top level exception handler */
JSONRpcClient.default_ex_handler = function (e)
{
alert("unhandled exception thrown in jsonrpc handler " + e);
};
If a json-rpc async handler itself throws and exception, it is often hard to
track down exactly where it's occuring (especially in IE) because the error
message is often very non-descript. (e.g. just [object Error])
When a handler itself throws an exception, I want to know about it
explicitly!
This has bitten me on more than one occasion-- often it took a while for me
to even realize it had anything to do with my json-rpc handler.
Agree? Disagree?
_______________________________________________
Jabsorb-dev mailing list
[email protected]
http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev
