HI All,
Thaks for your reply. I got a mail from Kevin Tarun. He has done it.
There is a way in ProGuard by which you can specify which methods and
classes not to obfuscate.
Warm Regards,
Allahbaksh
On Dec 10, 4:13 pm, Jason Morris <[EMAIL PROTECTED]> wrote:
> The obfuscator should either leave th
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
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]>
>
> HI Rob and Shawn,
> Thanks for your reply. I am thinking to use Pro
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]> wrote:
> On Tue, Dec 9, 2008 at 5:17 PM, Allahbaksh <[EMAIL
On Tue, Dec 9, 2008 at 5:17 PM, 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
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.
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
--~--~-~--~~~---~--~~
Yo
