[Wrapper-user] Re: Apache Launcher and Java Service Wrapper

[<da...@ix...>]

In article <3E6...@ou...>,
Richard Emberson  <wra...@li...> wrote:
>The launcher is basically and Ant task that knows how to launch
>a Java JVM subprocess allowing for the setting of system properties,
>class paths, arguments, etc.

I'm already doing this in one case by having wrapper launch ant which
launches an app (We're not done integrating everything yet, so need a 20
second or so start up delay which ant provides with it's <sleep/> task).

>With the launcher, the wrapper.conf "template" file is always the same,
>it simply calls on the launcher code passing in the name of the
>launcher.xml file. This file name is all that needs to change to
>call a different Java application (so it is parameterized - see
>include example).

Still, I'd rather avoid the extra layer if possible.

Still, I guess I should take the Unix tenet of "do one thing and do it
well" a bit more to heart.

>Java Service Wrapper is best at managing a Java application.
>Apache commons-launcher is best a launching a Java application.

>The next step for Java Service Wrapper is the registering of the
>wrapper on unix system so that on reboot the Java application
>starts.

Well, in theory, on systems that use SysV style init scripts, you should be
able to get away with linking results of sh.script.in into the appropriate
run level.  Of course, I believe that some systems, (AIX?) completely
rebuild those directories from scratch upon boot using a database.  And of
course, how to register is HIGHLY system dependent.  Heck, even among the
Linux distributions, init scripts don't end up in the same directory, or
use the same style!  I do think that this is more in the realm of a system
specific package tool.

mrc
-- 
     Mike Castle      da...@ix...      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc