if a ScheduledCommand throws an AssertionError then SchedulerImpl will never ever flushFinallyCommands() cause of entryDepth value greater than 0.
I I look at flushFinallyCommands and then runScheduledTasks I discovered that it catch RuntimeException (Hidden exception) but not Error.
This behavior make the page very unstable in debug mode for my bug. The expected behavior is to display my initial Error in the console.
Do i Have to fill a bug ?
thanks
laurent
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
No comments:
Post a Comment