After using Protector4J to process your application, a complete Tomcat runtime environment will be output in the output folder. You can use the startup.sh or startup.bat script in the bin directory to run the Tomcat program as in the past. Our customized version JRE is also in the bin directory, you can find a vlxjre folder there.
You can also find your application in the webapps directory, but the original WEB-INF/classes folder no longer exists. This is because in order to protect your application architecture so that external users cannot even obtain the name information of the class, we have packaged the content of WEB-INF/classes into WEB-INF/vlxapp.jar, which is a jarx format, It is the newly introduced format in Protector4J 2.0.
You may want to be able to update existing applications directly, without outputting a full Tomcat runtime environment each time
Protector4J will request a random and unique key from the server for every encryption task, and since the key is different for each task, the encrypted jar files obtained from different tasks cannot be used together. Therefore, we provide a KeySeed feature, the same KeySeed will generate the same key, and the jar files encrypted under the same KeySeed can be used together. Currently KeySeed is only available for licensed users.