This is an issue for your obfuscation vendor, not GWT. My guess is it will probably work, the existing Java obfuscators I have seen usually do the right thing. But Java is so dynamic with annotations and reflection it can be really hard to obfuscate it and still have something that actually runs.
Give it a try with your obfuscation vendor's tool, if it doesn't work, its probably an issue with their tool configuration. The GWT server side is just a Java servlet, nothing magical. Reflection usage is pretty typical; most tools should have switches you can use to ensure method names in your remote interfaces aren't obfuscated so the GWT RPCs can still complete normally. On Tue, Dec 9, 2008 at 08:17, Allahbaksh <[EMAIL PROTECTED]> wrote: > > Hi, > We are distributing an application. We want to obfuscate the server > side code to the client so that they should not reverse engineer the > code. Is it works fine? > > What will happend to servlets? Whether they work fine? > > Regards, > Allahbaksh > > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
