Java Reference
In-Depth Information
Caused by: java.lang.ClassNotFoundException: java.sql.SQLException
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
... 6 more
Deploying the Custom JRE
The directory specified as the
-d
(or
--dest
) option's value is the directory that contains all the required files for the
custom JRE. To deploy the JRE, you will need to copy all the files from the JRE directory to the target device. The actual
steps or commands needed to copy the JRE files vary from device to device. Please refer to the documentation for your
device on how to deploy the JRE files.
■
if you use the
jrecreate.bat
file on Windows to create the custom Jre, you will need to copy the Jre files
from Windows to the linux platform running on the device. in this case, the
java
command in the Jre bundle may not be
recognized as a command on the linux platform. After you copy the Jre files, you may have to run the following
command on linux to make the
java
file executable:
Tip
$ chmod +x java
Running the Custom JRE
Running the custom JRE on a device is the same as running any other JRE: run the
java
command from the
bin
directory in the deployed JRE directory. Sometimes you may have to set the
PATH
environment variable on the device
to point it to the
bin
directory containing the
java
command. Assuming that you have copied the custom JRE files
to the
/mydevice/jre8
directory on the device, you can use the following command to set the
PATH
environment
variable:
$ export PATH=$PATH:/mydevice/jre8/bin
