Hi.. My be this is silly to think "like lock on byte code"..but It may have its own advantages like no one can decompile the class file and get biz logic inside that.. I want to deliver my product to my client and I dont want let him know or modify the business logics used inside the code...Is there any way to protect the byte code from decompiling..
You could consider a ClassLoader that decrypts classes on loading. The Jars would contain classes encrypted before they were added to the Jars. Therefore, they wouldn't decompile with an ordinary decompiler.
This makes it harder for people to look at your bytecode, as they've either got to look at the code in-memory while executing (you can make this harder by preventing attachment of an ordinary debugger) or break the encryption.
Have no illusions that this will stop a smart, determined cracker, but it should stop a dumb or lazy one.
For hopefully-obvious reasons, I'm not posting any code, but you might like to consider this approach. It's not so very hard.
Betty Rubble? Well, I would go with Betty... but I'd be thinking of Wilma.