If you have the source code for a project and no specific Java 7 features are being used in the code, you could simply recompile it using JDK 1.6 or even 1.5. Compiling the Java project using JDK 1.6 instead of JDK 1.7.
It is worth considering a number of alternatives before trying to setup Matlab with the JVM 1.7: A future Matlab version (possibly as close as the upcoming R2013b) might be updated use Java 7 natively – the hacks should only be used on versions that have JVM 1.6.As with all other undocumented Matlab features, they may break in future Matlab versions.The set of hacks is not complete some issues remain in the setup of Matlab to use Java 7.Simulink or any Matlab toolboxes were not tested, nor any other operating systems (although I’ve found most solutions to work on Linux as well). The hacks described below were found to work for Matlab R2012b and R2013a on Windows 64bit.I urge readers to consider the following before trying the hacks I’ve found: Today’s article contains my experience in trying to let Matlab use JVM 1.7 code. However, although Java 7 has been available since July 2011, the latest official Matlab version (R2013a at this point) still uses the JVM 1.6 (Java 6), which does not allow calling Java 7 code directly. When running back-tests on our models I have to either ensure my Matlab prototype exactly matches the Java behavior, or to call the Java production code directly. The final production code is however coded by a separate development team in Java 7. I work in the team where I do a lot of research and prototyping with Matlab. Roderick discusses his experience with setting up Matlab to use the latest stable release of Java, namely JVM 1.7, a.k.a. Today I would like to introduce guest blogger Roderick, who wishes to remain anonymous.
0 kommentar(er)
