Why
Sometimes when you release a package on webMethods, you probably don't want to expose the detail of your Java service, so somebody else could not modify your code, or you just don't want them to know how genius you are. Well, there is an easy way to hide your Java code just like what they did for Wm* packages.
How
If you take a look into the folder which holds your Java service, you would see a file named "java.frag". It's actually an XML file which contains unreadable weird string. That weird string would be base64 decoded back to Java code exactly the same as what you would see in Designer. You could try to decode it on some free web site, for example https://www.base64decode.org.
What
To hide the Java code, you will need to remove all java.frag files when releasing the package. When you try to archive the package on IS Administrator UI, select "All except specified by filter:" and type "*.frag" as the filter value. Now your genius idea would be a secret.
But
Unfortunately, the secret won't be kept too long. Once somebody export your package to local, then they could decompile class file to find out what you're hiding. There is another way to hide Java code even after exporting the package, but that's another story.
No comments:
Post a Comment