[Wrapper-user] Re: different start/stop classes

[Leif M. <le...@ta...>]

Don,
I am cc-ing the wrapper-user mailing list. Please reply there and submit
any future posts to the list rather than to me directly.

Integration Method #2 does allow you to specify two different main
classes. Please reread them:
http://wrapper.tanukisoftware.org/doc/english/integrate-start-stop-win.html
The example used, Tomcat, specifies the same class for startup and
shutdown. But that is simply how Tomcat works. Your application will
be able to specify different classes.

From the docs:

# The first application parameter is the name of the class whose main
# method is to be called when the application is launched. The class
# name is followed by the number of parameters to be passed to its main
# method. Then comes the actual parameters.
wrapper.app.parameter.1=org.apache.catalina.startup.Bootstrap
wrapper.app.parameter.2=1
wrapper.app.parameter.3=start

# The start parameters are followed by the name of the class whose main
# method is to be called to stop the application. The stop class name
# is followed by a flag which controls whether or not the Wrapper should
# wait for all non daemon threads to complete before exiting the JVM.
# The flag is followed by the number of parameters to be passed to the
# stop class's main method. Finally comes the actual parameters.
wrapper.app.parameter.4=org.apache.catalina.startup.Bootstrap
wrapper.app.parameter.5=true
wrapper.app.parameter.6=1
wrapper.app.parameter.7=stop

Cheers,
Leif

Don Parker wrote:

>I am trying to use the wrappers in "integration mode 2" but 
>
>my start and stop classes are different.  It seems the 
>
>wrappers are designed to expect both functions to be 
>
>controlled from one main class.  Is there a way I can get 
>
>around this without having to implement my own 
>
>implementation for the WrapperListener?
>
>
>
>
>
>  
>