[born2c0de]

Java Decompilers are available on the web. The decompiling accuracy of these Applications is very accurate. It even decompiles J2ME code as well as J2EE code.

Is there any way to prevent Java code from being decompiled?
I've heard of Packers that are usually used to reduce executable size and to protect source code from being disassembled. But Packers only exist for EXE Files right? Or do they work for .class files as well?

[Amadeus]

Check out this forum. It suggests some Java Obfuscators.

[Amadeus]

This one is also good.

[stdunbar]

Realize that while there are obfuscators you can still jad the code and get a pretty good idea what is going on. Additionally, you can end up hurting yourself as your stacktraces can be hard to read. For example, for a Siebel integration I'm doing the wingnuts at Siebel must have used an obfuscator:

at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.e.a(Unknown Source)
at com.siebel.om.conmgr.d.d(Unknown Source)
at com.siebel.om.om.b.a(Unknown Source)
at com.siebel.data.SiebelDataBean.login(SiebelDataBean.java)

So what is the problem? In this case, what the heck was the point of obfuscating the code as you've got to have Siebel for it to work anyway.

That may not be your case but be warned that you may have issues like this. If a customer sends you a stacktrace even you might not know where the problem happened!

This post has been edited by stdunbar: 05 January 2005 - 01:07 PM

[born2c0de]

hmm...i never thought of that....interesting...