Thread: prevent class files from de-compilation in core java ??

I know the java code, class files. I know creating jar files and running jar files on Command Prompt

Recently, I have tried to create EXE Files with exe4j , jsmooth and "jar 2 exe"

But, I am not satisfied with all this. When I create exe file with exe4j and jsmooth, it run very well but "EXE" file require all class files for execution, if I place exe to a different place where class file is not present, it will not run..

Is there a way to convert jar file or all class files into exe files ?? I want to prevent my java class files from reverse engineering...

I am thinking to create an exe that will not require any class file for execution.

OR can you please tel me how to protect java class files so that they can never be de_complied with any de_compiler ??

I am looking forward to a positive reply from all online and offline users !

Originally Posted by Norm

I haven't heard of a way. obfuscation seems to be the only way to slow down someone from seeing your code.

I am tried of searching on internet !! I have searched and viewed a lot of pages that provides the suggestion obfuscation, but, I am unable to do anything practical code on obfuscation...

please provide some practical code to help me !!

can you tell about the working of progaurd ?? I have progaurd 4.11, it has bin folder, build folder , docs folder, example folder, lib folder and src folder , CO-PEG can you help me in making the class files much more secured ??

I know that there are professional tools that claim that they can transform any java application into a C++ application. So if you are really serious about it that would be an option for you.
But in general there is nothing you can do against reverse engineering of a java application. That is the case for all interpreted languages.

There are several tools for encrypting, obfuscating and licensing Java classes. Most work by wrapping your main class with their own, and encrypting the classes that are compiled with a shared key before assembling them into special jarfiles.

As an example, see: Wibu-Systems | Software Protection, Software Licensing, Access Protection, Document Protection - Wibu-Systems

There are others; I just happen to know about this one.