On Tue, Mar 15, 2011 at 09:46, Fritz Zaucker <[email protected]>wrote:
> the following scenario seems more difficult to debug than it could be:
>
> I have rpcAsync call that returns without error from the backend, e.g.
> exc
> is NULL.
>
> Within the callback of this rpcAsync() call I had a runtime error
> (trying to call some method on an undefined variable):
>
> myHandler: function(dataNew,exc,id) {
> if (exc == null) {
> var test;
> test.setValue(5); // runtime error from this
> }
> else {
> alert(exc);
> }
>
>
> The result was, I believe, that myHandler was called again, this time with
> exc set and resulting in something along the line "Local error 2".
>
> I don't quite understand was is going on, but to the unsuspecting user (as
> myself) it looked as if the backend did return an error (which it didn't).
>
> I think it would be helpful if runtime errors in the callback would be more
> easily be detectable (for example, by including a stack trace).
>
This has come up a number of times. Having thought about it, I believe it
should be easy to fix with a try/catch block around the call to the user's
callback. Please create a bugzilla entry. This should get fixed.
Thanks,
Derrell
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
