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