It is possible to make this setup work, but there are guidelines that must be adhered. Suppose that myLib1_5.jar was my library compiled with JDK 1.5, and matLib1_6.jar was the MATLAB deployed component compiled with JDK 1.6.
1. Java libraries compiled with older JDK versions cannot call libraries compiled with newer versions. So classes from myLib1_5.jar cannot call functions or classes from matLib1_6.jar.
2. Java libraries compiled with newer JDK versions may call libraries compiled with older versions.
3. Minor Java updates within a version such as 1.6.0-20 vs. 1.6.0-17 should not cause issues.
As such, there are two options to make the setup work:
1. Write a driver class, compiled in the newer version, that calls both the older version and the newer deployed component. For example, if myDriver1_6.class is my driver class compiled using JDK 1.6, it can call both myLib1_5.jar and matLib1_6.jar.
2. Call the older libraries from within MATLAB code using MATLAB's Java external interface, then deploy the whole component. For example, myLib1_5.jar is imported and utilized from the MATLAB code foo.m. Then foo.m is compiled into matLib1_6.jar using MATLAB Builder JA and JDK 1.6.
Please note that attempting to start MATLAB with an earlier version of JRE (setting MATLAB_JAVA environment variable to JRE 1.5), or attempting to compile the deployed component using an older JDK version (setting JAVA_HOME environment variable to JDK 1.5) are not possible.
