I guess, that your extra obfuscation step changes the names of all classes and thus the GWT serialization mechanism will not find the correct classes. I don't think you need to obfuscate anything, because GWT already obfuscates the java-script code: http://code.google.com/webtoolkit/doc/1.6/FAQ_DebuggingAndCompiling.html#Why_is_my_GWT-generated_JavaScript_gibberish
that means, all GWT code, that the client will ever see is already obfuscated: so why would you want to obfuscate the class files again? On May 26, 7:17 pm, Hedi Ben Said <hedi.bens...@gmail.com> wrote: > When I obfuscate a jar of a gwt application I got the following error > "The response could not be deserialized". > By obfuscating I do not mean the compiler option of gwt. I mean > obfuscating the .class files contained in the jar file > > Do you have any idea? > > Thanks a lot -- 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+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
