Re: Different approach to TC as a service (was: Separating Servicecode from Tomcat 4.0)

[cmanolache]

On Thu, 26 Jul 2001, Andy Armstrong wrote:

> By "conceptually portable" I mean that while the code in the connector
> to implement Tomcat startup and shutdown isn't the same for all
> platforms the concept of running Tomcat in that way is -- you can safely
> assume that whatever the platform the admin has already arranged for the
> web server to start automatically if that's what they want, and the
> arrangements for starting Tomcat at the same time are essentially the
> same across all platforms.

+1 for adding this in jk.

BTW, jk already has the feature if JNI connector is used - but it would be
great to be able to do the same for ajp connectors. Probably using the
same config file ( most of the information to start tomcat is similar -
the jni configuration file allows you to specify env variables,
classpaths, etc ).

One question - is anyone using the jk_service ( the NT service starter
that is included with tomcat3.x ) ?

( BTW, If you like modularity, it can even be developed as a separate
module,  independent of jk - that will keep the complexity under control.)


Costin