The obfuscator should either leave those method alone by default (since they're 
defined in an 
"outside" interface), or you should be able to configure it to leave them alone.

Either way, RemoteServiceServlet uses reflection and thus does need the method 
names intact. You may 
be able to alter the generated JavaScript code, or config to change the method 
names there as well, 
but I'm not sure how you would go about this. Easiest just to leave the method 
names alone.

Magno Machado wrote:
> Won't it break rpc?
> Unless your obfuscator keep the names of your services methods, I think 
> RemoteServiceServlet won't find them when you make a RPC call. But I'm 
> not sure about this..
> 
> 2008/12/10 Allahbaksh <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>>
> 
> 
>     HI Rob and Shawn,
>     Thanks for your reply. I am thinking to use ProGuard.Do you have any
>     other open source alternatives. Please let me know if you have used
>     any other?
>     Regards,
>     Allahbaksh
> 
>     On Dec 9, 9:35 pm, "Rob Coops" <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>> wrote:
>      > On Tue, Dec 9, 2008 at 5:17 PM, Allahbaksh
>     <[EMAIL PROTECTED] <mailto:[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
>      >
>      > Hi Allahbaksh,
>      >
>      > Obfuscating code is not going to stop any determined person from
>     reverse
>      > engineering your code, it might make it slightly more difficult
>     but that is
>      > about it. The code should still work otherwise the obfuscation
>     failed and
>      > you simply broke your own code.
>      >
>      > In the end any and all code you write can be reversed engineered
>     regardless
>      > of obfuscation or any other technique used to make it harder to
>     do so. So in
>      > that respect you will have to look at the cost you make
>     obfuscating your
>      > code as opposed to the risk you run with someone actually taking
>     the trouble
>      > of reverse engineering your code. How much will you loose if
>     someone reverse
>      > engineers your code in a week and how much will you loose if it
>     takes them a
>      > month... you might very well find that the cost of hiding you
>     code is not
>      > worth the money.
>      >
>      > Regards,
>      >
>      > Rob
> 
> 
> 
> > 

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

Reply via email to