Re: Error when obfuscating a gwt jar
3. All the classes, which reside only in server, are under your control and, hence, there is no need for any obfuscation. Maybe the server is not under the OP's control On Sun, May 29, 2011 at 11:27 PM, J.Ganesan j.gane...@datastoregwt.comwrote: External obfuscation seriously interferes with GWT. 1.Whatever is in client package, in any case, can not be obfuscated. 2. All the shared classes undergoing serialization can not be obfuscated. 3. All the classes, which reside only in server, are under your control and, hence, there is no need for any obfuscation. If the jar file you are talking about is a thrid party jar, you really have a problem. When there is an update of jar file, it will result in an incompatible serialization of the already saved objects. J.Ganesan www.DataStoreGwt.com On May 29, 5:59 pm, Hedi Ben Said hedi.bens...@gmail.com wrote: In my application besides the javascript that have been generated as a result for the gwt compilation, there is also a jar file that contains the classes of my gwt application. These classes are necessary to make the server and client part communicate via rpc On May 27, 11:24 am, Martin Trummer ds.martin.trum...@gmail.com wrote: 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 toobfuscateanything, because GWT already obfuscates the java-script code: http://code.google.com/webtoolkit/doc/1.6/FAQ_DebuggingAndCompiling.h... that means, all GWT code, that the client will ever see is already obfuscated: so why would you want toobfuscatethe class files again? On May 26, 7:17 pm, Hedi Ben Said hedi.bens...@gmail.com wrote: When Iobfuscatea 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. -- Magno Machado Paulo http://blog.magnomachado.com.br http://code.google.com/p/emballo/ -- 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.
Re: Error when obfuscating a gwt jar
In my application besides the javascript that have been generated as a result for the gwt compilation, there is also a jar file that contains the classes of my gwt application. These classes are necessary to make the server and client part communicate via rpc On May 27, 11:24 am, Martin Trummer ds.martin.trum...@gmail.com wrote: 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 toobfuscateanything, because GWT already obfuscates the java-script code:http://code.google.com/webtoolkit/doc/1.6/FAQ_DebuggingAndCompiling.h... that means, all GWT code, that the client will ever see is already obfuscated: so why would you want toobfuscatethe class files again? On May 26, 7:17 pm, Hedi Ben Said hedi.bens...@gmail.com wrote: When Iobfuscatea 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.
Re: Error when obfuscating a gwt jar
As already said, if you obfuscate rpc related classes, gwt will not be able to find them in order to make rpc work. You can obfuscate everything else, but not rpc stuff, afaik On Sun, May 29, 2011 at 9:59 AM, Hedi Ben Said hedi.bens...@gmail.comwrote: In my application besides the javascript that have been generated as a result for the gwt compilation, there is also a jar file that contains the classes of my gwt application. These classes are necessary to make the server and client part communicate via rpc On May 27, 11:24 am, Martin Trummer ds.martin.trum...@gmail.com wrote: 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 toobfuscateanything, because GWT already obfuscates the java-script code: http://code.google.com/webtoolkit/doc/1.6/FAQ_DebuggingAndCompiling.h... that means, all GWT code, that the client will ever see is already obfuscated: so why would you want toobfuscatethe class files again? On May 26, 7:17 pm, Hedi Ben Said hedi.bens...@gmail.com wrote: When Iobfuscatea 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. -- Magno Machado Paulo http://blog.magnomachado.com.br http://code.google.com/p/emballo/ -- 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.
Re: Error when obfuscating a gwt jar
External obfuscation seriously interferes with GWT. 1.Whatever is in client package, in any case, can not be obfuscated. 2. All the shared classes undergoing serialization can not be obfuscated. 3. All the classes, which reside only in server, are under your control and, hence, there is no need for any obfuscation. If the jar file you are talking about is a thrid party jar, you really have a problem. When there is an update of jar file, it will result in an incompatible serialization of the already saved objects. J.Ganesan www.DataStoreGwt.com On May 29, 5:59 pm, Hedi Ben Said hedi.bens...@gmail.com wrote: In my application besides the javascript that have been generated as a result for the gwt compilation, there is also a jar file that contains the classes of my gwt application. These classes are necessary to make the server and client part communicate via rpc On May 27, 11:24 am, Martin Trummer ds.martin.trum...@gmail.com wrote: 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 toobfuscateanything, because GWT already obfuscates the java-script code:http://code.google.com/webtoolkit/doc/1.6/FAQ_DebuggingAndCompiling.h... that means, all GWT code, that the client will ever see is already obfuscated: so why would you want toobfuscatethe class files again? On May 26, 7:17 pm, Hedi Ben Said hedi.bens...@gmail.com wrote: When Iobfuscatea 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.
Re: Error when obfuscating a gwt jar
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.
Error when obfuscating a gwt jar
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.
