In many cases for me, the pesky errors would only happen in IE -- but that's
a good idea, regardless.
On Wed, Aug 27, 2008 at 4:22 PM, William Becker <[EMAIL PROTECTED]> wrote:
> It would be good to also check for firebugs console.log and to use that as
> well, as it allows the error to be inspected in more detail.
>
> On Wed, Aug 27, 2008 at 7:13 PM, Arthur Blake <[EMAIL PROTECTED]>wrote:
>
>> 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
>>
>>
>
> _______________________________________________
> Jabsorb-dev mailing list
> [email protected]
> http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev
>
>
_______________________________________________
Jabsorb-dev mailing list
[email protected]
http://lists.jabsorb.org/mailman/listinfo/jabsorb-dev
