Use this methods

First, include a GWT.uncaugthExceptionHandler() into the code to log
the error
Second, with Firebufg you can use console.log (into native code, I
think ) to log to Firebug.
Try to generate js code in PRETTY mode to have a good look to where
the code is making an error


Hope it helps


On 3 mar, 14:12, Pawel <[email protected]> wrote:
> Hi,
>
> I'm using GWT for my Bachelor Thesis. I started developing a
> Application when GWT 1.7 was out and as I'm afraid something could
> crash updating to 2.x I'm still working with that version.
>
> Well, my Problem is, that in Hosted Mode my application runs without
> errors. Even when I compile it (pressing the "Compile/Browse" button
> in the hosted modes browser) and view it in any Browser (FF,
> Safari,...) everything is ok.
> Being ready to deploy it to another server (Tomcat) I compiled my app,
> packed it as a war and deployed it to a Tomcat server on another
> machine.
> Now, the app starts in the browser. RPC works, as I'm getting Data
> from the Server, but at some Point the app simply stops with errors
> displayed by Firebug.
>
> I'm going to debug what excatly is not working there, but since the
> same compiled files delivered by jetty locally are causing no problems
> (viewing the compiled version with FF, ...) I'm curious if someone did
> have similar problems and could point me in some directions which
> could help me find the cause of that odd behaviour.
>
> thx in advance
> Pawel

-- 
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.

Reply via email to