tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Gooding <>
Subject Re: Just a few questions on my Tomcat Configuration
Date Mon, 22 Jun 2009 19:26:30 GMT
Once again (sigh) .....

I just got out of my management meeting, they want to know if it can be done
the "other" way, with all companies sharing the core code.  I'm not exactly
sure on how I'd even begin to do this.  While I made a good point that A -
it's more secure, and B - it is the better way of doing things, they did
countered.  If we wanted to upgrade the software, it's better to upgrade one
single install, than to upgrade 50 - 100 clients which takes a large amount
of time.  It then becomes a logistical issue.  All that aside, would you
have any clue as to how would I go about starting something like that?  I'm
going to check the docs more closely, however, I am not confident that I
will find anything like that in there.

- Josh

On Wed, Jun 17, 2009 at 10:10 PM, Caldarale, Charles R <> wrote:

> > From: Josh Gooding []
> > Subject: Re: Just a few questions on my Tomcat Configuration
> >
> > Maybe each company would have a customized few pages each with
> > their own directories, tied to their own schema, etc, but point
> > to the core application in another directory.  Everyone would
> > see their own front ends, but use a common "framework" in the
> > backend maybe?
> That's quite a bit more than I was referring to, and I find it unlikely
> that any company would want its processing to be shared with others in the
> same webapp.  Better to have separate deployments for each, even if the
> underlying webapp is identical in each instance.
> > Are those API's part of teh standard Tomcat docs?
> The ones I referred to for adding and removing <Host> elements dynamically
> are part of the Embedded class:
> The doc states that components can be added and removed on the fly, even
> after the start() method has been invoked.  I've never tried it.
>  - Chuck
> MATERIAL and is thus for use only by the intended recipient. If you received
> this in error, please contact the sender and delete the e-mail and its
> attachments from all computers.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message