Well, since most of the code is pretty straigh-forward there is no real danger from my
point of view. Surely if you implement some custom shared-key security in an open
system it could be an issue. Again
because your servlets are not available publicily (like say applets) there is i should
say a comparably only minor risk.
There are some programs which are tinkering with the class code and make it
'undecompilable' to some degree. Basic idea is to insert some names which would be
invalid in Java code but are still executable
by JVM. I'm routinely decompile applets and haven't come upon anything like that so
far.
By the way there is a pretty good free decompiler called 'JDE'. It is not Java (as
some decompilers are) but there a versions for different systems.
Jackson Ching wrote:
> Hi,
>
> Correct me if i'm wrong, Since class file can be decompiled, and servlets
>are on server side, wouldn't it be dangerouse if your servlets can be decompiled by
>hackers (they can know your codes).
>
> Is there a way for your class files not to be reverse engineered?
>
> Jack
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
