Java Advanced Imaging ImageIO Tools
This article captures current information about the Java Advanced Imaging ImageIO Tools to document exactly what files are involved.
The ImageIO Tools consist of two jar files plus one or more files which are in native code for the platform.
1 JAR Files
|File name||Description||Typical Location|
|jai_imageio.jar||JAR file containing core JAI Image I/O class files.||jre/lib/ext|
|clibwrapper_jiio.jar.||codecLib JNI interfaces.||jre/i386||jre/lib/ext|
2 Native Libraries
|File name||Description||Platform||Typical Location|
|libclib_jiio.so||mediaLib JNI shared libraries||Linux||jre/i386|
|clib_jiio.dll||codecLib JNI shared libraries||Windows||jre/bin|
|clib_jiio_sse2.dll||mediaLib JNI DLL libraries||Windows||jre/bin|
- The jar files are typically located in the Java jre/lib/ext directory.
- The dll files are typically located in the Java jre/bin directory on a Windows system.
- The so file is typically located in the Java jre/i386 directory on an Intel Linux system.
- All the binary builds are available on https://jai-imageio.dev.java.net/binary-builds.html
- The jar files are required.
- The dll/so files provide acceleration for certain image types.
- The dll/so files may also provide support for additional image types.
- You can force the ImageIO Tools not to use the native libraries by starting a program with this switch:
At one time, the following was true (according to jgarnet):
If use of native code is disallowed then the JPEG and PNG reader-writer plug-ins and some accelerations used for bilevel TIFF compression will not be available nor will the native implementation of the JPEG 2000 reader-writer plug-in; the Java implementation of the JPEG 2000 plug-in will however be available. The respective plug-ins will detect that native libraries cannot be used and respond accordingly.