You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by "Steven J. Owens" <pu...@darksleep.com> on 2004/11/06 09:20:46 UTC
Re: Configuration Management, JSP Recompiles, War Files
On Mon, Oct 25, 2004 at 09:15:41AM -0400, Shapira, Yoav wrote:
> > If I understand correctly, WAR file is just a glorified JAR file,
> >which in turn is just a glorified tar file. So unless you're
> >unjarring it, editing the config file and rejarring it, you can't
> >really muck with the config settings inside it. How/where do people
> >normally keep the configuration variables for the webapp?
>
> You might want to read up the Servlet Spec's section on resource-ref and
> env-entry refs. These provide a way for you to keep one WAR and edit
> server.xml (or another server-specific, outside-your-WAR configuration
> file) to modify configuration information. Your understanding above is
> incomplete.
So the standard practice is to put all of your configuration
variables in server.xml and reboot the server if you need to change
the configuration?
--
Steven J. Owens
puff@darksleep.com
"I'm going to make broad, sweeping generalizations and strong,
declarative statements, because otherwise I'll be here all night and
this document will be four times longer and much less fun to read.
Take it all with a grain of salt." - http://darksleep.com/notablog
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
Re: Configuration Management, JSP Recompiles, War Files
Posted by "Steven J. Owens" <pu...@darksleep.com>.
On Sat, Nov 06, 2004 at 03:20:46AM -0500, Steven J. Owens wrote:
> On Mon, Oct 25, 2004 at 09:15:41AM -0400, Shapira, Yoav wrote:
> > > If I understand correctly, WAR file is just a glorified JAR file,
> > >which in turn is just a glorified tar file. So unless you're
> > >unjarring it, editing the config file and rejarring it, you can't
> > >really muck with the config settings inside it. How/where do people
> > >normally keep the configuration variables for the webapp?
> >
> > You might want to read up the Servlet Spec's section on resource-ref and
> > env-entry refs. These provide a way for you to keep one WAR and edit
> > server.xml (or another server-specific, outside-your-WAR configuration
> > file) to modify configuration information. Your understanding above is
> > incomplete.
>
> So the standard practice is to put all of your configuration
> variables in server.xml and reboot the server if you need to change
> the configuration?
Ah, your further comments in "RE: discussion on webapp reload in
production" indicates that restarting tomcat for changes is indeed
standard practice. Okay.
Is there a HOWTO or tutorial anywhere on running an ASP style
setup (er, that's application service provider, not the other ASP)
with multiple apps, using tomcat? More of a "standard practices" sort
of thing, though how-to/tutorials for specific aspects would also be
cool.
--
Steven J. Owens
puff@darksleep.com
"I'm going to make broad, sweeping generalizations and strong,
declarative statements, because otherwise I'll be here all night and
this document will be four times longer and much less fun to read.
Take it all with a grain of salt." - http://darksleep.com/notablog
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org