Hi,
I would recommend the following;
1) Add a uncaught exception handler and if that doesn't solve the
issue
2) pick a log library gwt-log or i_log (my adligo packages)
direct the log output back to the server, so you can determine
where the code is blowing up, add a try catch to catch your
exception. As a last resort work in halves to determine the location
of the blowup.
Cheers,
Scott
On Oct 20, 1:29 pm, Ian Bambury <[email protected]> wrote:
> Hi Sudeep,
> This, in my experience, is usually due to IE being politically correct and
> FF being lenient (as opposed to FF being correct and IE being complete ****,
> which is what people would tell you if things were the other way around)
>
> Assuming you are on Linux and using something less that GWT v2.0, then the
> easiest way to sort it out is to run the project on a Windows machine (since
> hosted mode uses IE and you'll get an error with a line number)
>
> If that isn't an option, then compile with -style PRETTY or DETAILED, which
> will at least tell you the method that is failing - have a look at it, and
> post again if you can't see the problem.
>
> Ian
>
> http://examples.roughian.com
>
> 2009/10/20 Sudeep S <[email protected]>
>
> > hello,
>
> > I hav my gwt app, compiled and running fine on FF,
>
> > but on IE it says that *this.h.a* is null or not an object.
>
> > Any ideas how to debug/backtrack the java code for such an error.
>
> > Thanks
> > Sudeep
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
