On 25/09/2009 14:03, Pid wrote:
On 25/09/2009 08:26, hepabolu wrote:
awarnier wrote:
hepabolu wrote:
...
However, from the Tomcat docs I understand that any change to
server.xml
requires a restart of Tomcat which would mean that the existing
(non-dummy)
hosts which are already in productio
On 25/09/2009 08:26, hepabolu wrote:
awarnier wrote:
hepabolu wrote:
...
However, from the Tomcat docs I understand that any change to server.xml
requires a restart of Tomcat which would mean that the existing
(non-dummy)
hosts which are already in production, i.e. up and running, will also
awarnier wrote:
>
> hepabolu wrote:
> ...
>
>> However, from the Tomcat docs I understand that any change to server.xml
>> requires a restart of Tomcat which would mean that the existing
>> (non-dummy)
>> hosts which are already in production, i.e. up and running, will also be
>> taken offline.
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Friday, September 18, 2009 3:26 PM
> To: Tomcat Users List
> Subject: Re: Virtual host configuration - best practise?
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: S
pdating files
anyway, I preferred a more obvious method.
-Original Message-
From: George Sexton [mailto:geor...@mhsoftware.com]
Sent: Friday, September 18, 2009 2:15 PM
To: 'Tomcat Users List'
Subject: RE: Virtual host configuration - best practise?
> -Original Message-
Caldarale, Charles R wrote:
>
>> From: hepabolu [mailto:hepab...@gmail.com]
>> Subject: Re: Virtual host configuration - best practise?
>>
>> Somebody suggested using the host manager, but from the Tomcat docs I
>> understand that the host manager is in
> From: hepabolu [mailto:hepab...@gmail.com]
> Subject: Re: Virtual host configuration - best practise?
>
> Somebody suggested using the host manager, but from the Tomcat docs I
> understand that the host manager is intended for deploying webapps in a
> single domain
No, that
hepabolu wrote:
...
However, from the Tomcat docs I understand that any change to server.xml
requires a restart of Tomcat which would mean that the existing (non-dummy)
hosts which are already in production, i.e. up and running, will also be
taken offline. This is the heart of the problem...
J
Hi,
Christopher Schultz-2 wrote:
>
> It's been demonstrated that you can use the XML parser to include one
> XML file in another file (say, include myhosts.xml from server.xml).
> Given that, you could have a process whereby you update Tomcat
> on-the-fly, but also modify the myhosts.xml file a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
George,
On 9/18/2009 3:15 PM, George Sexton wrote:
> No. Use the host manager to deploy/undeploy virtual hosts on the fly. When
> you re-start tomcat, have a program create the server.xml so that all of the
> one's you deployed using the host manager
> -Original Message-
> From: hepabolu [mailto:hepab...@gmail.com]
> Sent: Friday, September 18, 2009 1:06 PM
> To: users@tomcat.apache.org
> Subject: RE: Virtual host configuration - best practise?
>
>
>
>
> George Sexton wrote:
> >
> >
>
George Sexton wrote:
>
>
> Another way of getting there is scripting commands to the Tomcat Host
> Manager application. You can deploy the new hosts on the fly. It's pretty
> straight forward.
>
> The downside to this approach, and probably JMX as well is that it doesn't
> update server.xml a
> -Original Message-
> From: Mark Thomas [mailto:ma...@apache.org]
> Sent: Friday, September 18, 2009 11:12 AM
> To: Tomcat Users List
> Subject: Re: Virtual host configuration - best practise?
>
> hepabolu wrote:
> > Hi,
> >
> > I need to cre
hepabolu wrote:
> Hi,
>
> I need to create the following situation:
> - each client uses a war (all use the same war file) with configuration
> files that are different for every client
> - each client's configuration should be addressable by a different URL, e.g.
> domainX, domainY
>
> So in To
14 matches
Mail list logo
