You probably want to start with org.apache.tomcat.modules.config.NSConfig
(it's 3.3 name, I don't know where it lives in 4.0), and see what needs to
be changed to go from NS->iPlanet.
----- Original Message -----
From: "Colin Wilson-Salt" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 09, 2001 10:15 AM
Subject: RE: Web server integration / NameTrans stage
> But... you still need to edit the web server configuration file to deploy
a
> web app. If the file that describes how the two pieces integrate is owned
by
> the tomcat user, then the Java guys can look after that and the only thing
> that they need to do with iPlanet is use its admin tool to restart it.
>
> iPlanet is not nice to configure, it's not very forgiving (a single space
in
> the wrong place can prevent it starting with no sensible error message),
and
> its configuration files are typically owned by root - I want to let the
> webapp coders deploy their applications, but I don't want them anywhere
near
> the web server that I've spent so long configuring and tuning.
>
> > -----Original Message-----
> > From: Pier P. Fumagalli [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, August 09, 2001 17:13
> > To: [EMAIL PROTECTED]
> > Subject: Re: Web server integration / NameTrans stage
> >
> ...
> >
> > I suppose that JK has something like that. They rely on external
> > configuration files. Regarding mod_webapp, external
> > configuration files are
> > a big -1... No-No... Configuration should be effective, minimal and
> > integrated with the web-server... If you see how Apache
> > works, you have only
> > ONE line of configuration per web-application, and all the
> > rest is taken
> > care automatically...
> >
> > Pier
> >
>
>
