java - Jar Protection other than obfuscation -

i have tricky situation in protect jar file available in clients machine.

i have java project , using build.xml generate jar file available @ client machine post installation.

now need protect code available in jar file if @ client/s try decompile , see code base.

i have dependency in when client tries trigger project using ui, i generate java file in server , download java file @ client machine , compile java file .class. java file been downloaded client machine refer jar file , functions inside jar.

i worried if code obfuscation using proguard or other tools, all function names gets changed in jar , the java file downloaded not compile in client machine due mismatch in function calls java file has , jar has.

i can't change of server side logic generating java file , being downloaded client machine @ runtime.

i wanted logic wanted protect jar file @ clients machine without breaking compilation. don't want client see code using jar available in machine.

any highly appreciated, in advance

if using proguard, interested in processing callback methods:

if application, applet, servlet, library, etc., contains callback methods, called external code (native code, scripts,...), you'll want preserve them, , classes too. entry points code, like, say, main method of application. if aren't preserved other -keep options, following option keep callback class , method:

-keep class mypackage.mycallbackclass {     void mycallbackmethod(java.lang.string); } 

this preserve given class , method being removed or renamed.

if there limited amount of methods , classes want externally call, rename them (minify) on own before obfuscation takes place; thus, add own obfuscation/minification on methods. use minified names client's program. rest proguard obfuscate.