NavigationUser login |
Changing a FI Connect class fileSpecific instructions for recreating a FI Connect class file, but the idea works for most any other applications non-obfuscated java class file. 1. Create working environment similar to the FI Connect application under Tomcat on a) the Unix box running FI Connect (insures JRE match when doing java compile) in a working directory, and b) on your PC. Copy everything under ../webapps/fixml into a new directory on the Unix box, say /home/user, so $HOME/fixml matches ../webapps/fixml, all its files and subdirectories. Copy everything again into a directory on your PC. 2. Create jar files containing all existing class files in your Unix environment. cd $HOME/fixml/WEB-INF/classes zip ./com/iint/ic/app/app.zip ./com/iint/ic/app/* Rename app.zip and util.zip to app.jar and util.jar. 3. Copy class file to your PC. Use FTP to copy ../webapps/fixml/WEB-INF/classes/com/iint/ic/app/Vendor.class into its equivalent directory on your PC. 4. Decompile the class file. The decompiler needs the directory structure and other class files. 5. Edit the file and save it as a .java file, example Vendor.java. 6. FTP the java file into your Unix working environment. 7. Compile the java file in your Unix working environment. It’s important that you do the compile using javac in a directory with oversight over all directories and files needed by the java file. In most cases this is $HOME/fixml/WEB-INF/classes. The compile command is: A class file is created in the same directory as the java file. It’s possible to compile the class file on your PC, but then you have to pay attention to what JRE is going to be used on your PC and that it matches the JRE used on the Unix box, else you’re going to get a JRE mismatch error in the application. 8. Copy the new class file from the Unix working environment in the FI Connect directory. 9. Tomcat needs to be bounced whenever a class file is changed. Reply |