Hi Dennis, Well, this is not the case. I am not changing any field or adding new ones to serialized objects... The issue occurs even if I change some logic within the method, or add new element to a container, etc and hit browser refresh
Thanks, Ankit On Dec 29, 1:00 pm, Dennis Haupt <[email protected]> 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. > > -- -- 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.
