|
Java Classpath to use.
You should have a series of properties listing up the various class path elements
to use when launching the application.
Each element has a property name which starts with
wrapper.java.classpath.
and the "<n>" component of the property name is an integer number counting up from "1".
By default, there can be no missing numbers. The
wrapper.ignore_sequence_gaps
property can optionally be set to allow gaps in the sequence.
This list must contain the
wrapper.jar file.
It can contain jar files as well as directories containing class files.
| Example: |
wrapper.java.classpath.1=../lib/wrapper.jar
wrapper.java.classpath.2=../lib/myapp.jar
wrapper.java.classpath.3=../lib/mysql.jar
wrapper.java.classpath.4=../classes
|
If a wildcard character is used within a classpath entry,
all matching files will added to the classpath used when launching a JVM instance.
Valid wildcard characters are
-
'*': will match "0" (zero) or more characters.
-
'?': will match exactly one character.
Sort:
Starting with version 3.3.8,
the Wrapper now sorts lists of jar files matched
by an individual classpath property containing wildcards.
This is done to make sure that the exact same classpath
is used on all installations of an application.
Normally this would not be an issue,
however sometimes a resource file or class is duplicated in more than one jars.
By controlling the order of the jars,
it is guaranteed that the same version will always be used.
| Example: |
wrapper.java.classpath.1=../lib/*.jar
wrapper.java.classpath.2=../classes
|
Environment variable:
If you wish to include a system defined classpath as part of the Wrapper's classpath,
you can do so by referencing the appropriate environment variable.
The resulting
wrapper.conf
file will still be cross platform compatible
because the path separator in the included classpath
will always be correct for the current platform.
| Example (referencing environment variable): |
wrapper.java.classpath.1=%CLASSPATH%
|
Problems?:
If you encounter any problems related to classpath,
the first thing that should be done is
to verify the full classpath being generated by the Wrapper.
To do this, either enable debug log output with the
wrapper.debug
property, or enable the display of the Java command using the
wrapper.java.command.loglevel
property.
|
NOTE
|  |
No Quotes, and Individual Path Entry :
Generally, Windows will correctly handle path elements which contain spaces
by enclosing the path in quotes.
However, Wrapper can correctly handle path elements including spaces,
so they should not be quoted even if spaces are contained.
In addition, when you have several multiple path elements,
each path element should be spesified individually in quotes
WITHOUT enclosing the final combined path in quotes with semicolon separators in one line.
|
|
