Mac OS X
Components Crossplatform Mac & Win Server (Not) Client Old Guides Examples
New in version: 6.5 7.0 7.1 7.2 7.3 7.4 7.5 8.0 8.1 8.2 Statistic
|Component||Version||macOS||Windows||Server||FileMaker Cloud||FileMaker iOS SDK|
|LibPath||Path to java library (e.g. jvm.dll)
If empty, the plugin uses the Java framework on Mac and looks into registry on Windows to find newest Java installation.
e.g. on Windows:
|ClassPathList||The list of native paths to the jar files to load.
Please pass here all jar files you want to use.
Pass a parameter for each additional option to pass to Java VM initialization.
Returns OK or error.
You can either pass path to jvm library file or let the plugin look for it. To access classes, you need to pass paths to the jar and class files you want to use.
Returns error if already a JavaVM is initialized.
Please be aware that you can only have one VM running at a given time, so you can’t use Java in other plugin and our plugin together.
This should work fine for any Java version starting with 1.4 or newer. Tested with 1.7 and 1.8.
May not initialize probably if other plugin initialized Java before.
Returns "Using existing Java VM." in case an existing Java VM initialized by other plugin is used. In that case we can't pass your class paths or other options!
This function requires a native path. Use Path.FileMakerPathToNativePath to convert a FileMaker path to a native path if required. If you like to have the user choose the path, you can use FileDialog functions.
For Server be aware that server has limited permissions and may not be able to access all files on a computer.
Initialize on Linux:
Init with three class path entries:
Feedback: Report problem or ask question.
MBS FileMaker blog