Hell Björn, I know your pain. In this case you have really only one option: loggin! Grab yourself a nice div somewhere on your page and start mercelessly logging what your application is doing to that div and try to narrow down where the error happens.
Also try/catch block which Window.alert() the exception will help you close up on the error fast. On Jul 16, 9:29 am, Björn <[email protected]> wrote: > Hi again, > > bad news. I got the same result with 2.0.3. > > Our project is working with the gwt quite happy for the last 4 years. > But this situation has allways been in the top 3 topics of our risk > list. > > Any thoughts would be greatly appreciated. > > Björn -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
