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 ends with an integer number counting up from 1. There can
be no missing numbers.
This list must contain the
wrapper.jar file. It can
contain jar files as well as directories containing class files.
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
'*' and
'?'.
'*' will match 0 or more
characters and '?' will match
exactly one character.
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:
wrapper.java.classpath.1=%CLASSPATH%
Whenever any classpath related problems are encountered, 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
On Windows, the Wrapper will correctly handle class path
elements which contain spaces by enclosing the final combined
class path in quotes. Individual class path elements should
not be quoted even if they contain spaces.