On 26 Jan., 20:51, John Denley <johnvden...@googlemail.com> wrote: > This is beyond anything Ive come across before, sorry I cant help anymore, > though it looks like i did manage to push you in the right direction!.... > > good luck figuring it out...
I finally did. The root cause was a programming error on my behalf, where an object might be null if some methods were invoked in the wrong order. This introduced a nasty timing-dependant error. The actual subject of mu posting is still unresolved, however: It is very hard to figure out the area of the original Java code responsible for an exception thrown at runtime. I understand that a better stack trace mechanism is in the works, but obviously it is not yet part of the production branch of GWT. In the mean time we are left to our most ancient tools, the printf and our naked brain :) Regards, and thanks for the help all Anders -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
