Re: GWT debug

Here is a fresh error log

13:45:39.163 [ERROR] [dealmanager] Uncaught exception escaped

com.google.gwt.core.client.JavaScriptException: (Error): Invalid
argument.
number: -2147024809
description: Invalid argument.
at
com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:
195)
at
com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:
120)
at
com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:
507)
at
com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:
264)
at
com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:
91)
at com.google.gwt.core.client.impl.Impl.apply(Impl.java)
at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:188)
at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103)
at
com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71)
at
com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:
157)
at
com.google.gwt.dev.shell.BrowserChannel.reactToMessages(BrowserChannel.java:
1668)
at
com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:
401)
at
com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:
222)
at java.lang.Thread.run(Thread.java:619)

Thanks,
Ankit

On Dec 29, 1:00 pm, Dennis Haupt <d.haup...@googlemail.com> wrote:
> Am 29.12.2011 17:15, schrieb Anky:
>
>
>
>
>
> > Hi All,
>
> > I am not sure if it is a problem with my application.
>
> > Initially when we started development, the debug worked fine, with few
> > exceptions of hitting the browser refresh button couple of times to
> > get the code picked by debugger.
>
> > Now our application has grown up considerably and our debug
> > environment does not work often. We change code, hit the browser
> > refresh and we get a message that 'response cant be deserialized' and
> > sometime on second hit of browser refresh it display message related
> > to JNSI. This forces us to recompile the GWT code and deploy again. I
> > think it eats up considerable development time.
>
> > Has anyone experienced this problem with large app development using
> > GWT?
>
> > Thanks,
> > Ankit
>
> if you change a class that is being serialized - for example add a field
> - you'll get this error because the server and client are no longer in
> sync. if there is a way to fix that, i'll be glad to know.
>
> --- Hide quoted text -
>
> - Show quoted text -

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