| Compatibility : |
1.0.0
|
| Editions : |    |
| Platforms : |          |
Class to execute when the Wrapper starts the application.
The value of this property depends on which of the
Integration Methods that were selected.
In most cases, this is NOT the main class of your application.
| Example: (Integration Method 1: "WrapperSimpleApp") |
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperSimpleApp
|
| Example: (Integration Method 2: "WrapperStartStopApp") |
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp
|
| Example: (Integration Method 4: "WrapperJarApp") |
wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperJarApp
|
If you specify a main class which does NOT correctly initialize the WrapperManager class,
then the Wrapper will timeout and terminate the JVM after the startup timeout has expired.
Please see the wrapper.startup.timeout property
for more details. When this happens, you will see a message like the following:
------------------------------------------------------------------------
Advice:
The Wrapper consists of a native component as well as a set of classes
which run within the JVM that it launches. The Java component of the
Wrapper must be initialized promptly after the JVM is launched or the
Wrapper will timeout, as just happened. Most likely the main class
specified in the Wrapper configuration file is not correctly initializing
the Wrapper classes:
com.myapp.Main
While it is possible to do so manually, the Wrapper ships with helper
classes to make this initialization processes automatic.
Please review the integration section of the Wrapper's documentation
for the various methods which can be employed to launch an application
within the Wrapper:
http://wrapper.tanukisoftware.org/doc/english/integrate.html
------------------------------------------------------------------------
|
|
