Re: Context management and virtual host

2002-08-26 Thread Craig R. McClanahan

There is no current support for a manager webapp that works cross-host.
The people I know using multiple virtual hosts haven't had any problems
with the notion of installing manager in each host (usually with a unique
username/password if you allow the virtual host users to manage their own
webapps).

Admin webapp support for contexts is primarily for tweaking existing
config properties.  I view manager as the standard mechanism for dynamic
starting and stopping of webapps, in addition to deploying, undeploying,
and reloading.  Although the user interface of manager is quite limited,
it is expressly designed to be used by tools -- such as the Ant custom
tasks included in Tomcat 4.1, and the version of deploytool shipped with
the JWSDP http://java.sun.com/webservices/.

People building plugins for IDEs should really be integrating support for
manager commands instead of trying to embed Tomcat inside their
environments.  They'd find it a lot easier.

Craig


On Mon, 26 Aug 2002, Q. Werty wrote:

 Date: Mon, 26 Aug 2002 16:42:32 +0200
 From: Q. Werty [EMAIL PROTECTED]
 Reply-To: Tomcat Users List [EMAIL PROTECTED]
 To: [utf-8] tomcat-user [EMAIL PROTECTED]
 Subject: Context management and virtual host

 I'am looking for a way to manage all contexts installed on my
 server.
 I've got numerous virtual hosts and I'like NOT to install
 manager context in all virtual hosts. How can I do?
 - Is it possible to install a cross-host context in Tomcat?
 - I saw the administration interface in Tomcat 4.1 beta. It's a
 very great work, this interface enable to see/add/remove all
 contexts accross all virtual hosts. I thought it was what I was
 looking for but apparently there's nothing to start/stop/reload
 context. Is it planned for final version?

 Thanks in advance for any response

 Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET 
(0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Context management and virtual host

2002-08-26 Thread Q. Werty

I agree there's no problem with installing the manager
application in each virtual host. I just don't want to do this
because I don't want to publish this context to anyone, even
with credentials.
I would be ready to this on our production server if I could
restrict manager context access to some IP adresses (127.0.0.1
for exemple).
== Is it possible? (if not, what about thinking of this in
future release?)



 There is no current support for a manager webapp that works
cross-host.
 The people I know using multiple virtual hosts haven't had
any problems
 with the notion of installing manager in each host (usually
with a unique
 username/password if you allow the virtual host users to
manage their own
 webapps).

 Admin webapp support for contexts is primarily for tweaking
existing
 config properties.  I view manager as the standard mechanism
for dynamic
 starting and stopping of webapps, in addition to deploying,
undeploying,
 and reloading.  Although the user interface of manager is
quite limited,
 it is expressly designed to be used by tools -- such as the
Ant custom
 tasks included in Tomcat 4.1, and the version of deploytool
shipped with
 the JWSDP http://java.sun.com/webservices/.

 People building plugins for IDEs should really be integrating
support for
 manager commands instead of trying to embed Tomcat inside
their
 environments.  They'd find it a lot easier.

 Craig


 On Mon, 26 Aug 2002, Q. Werty wrote:

  Date: Mon, 26 Aug 2002 16:42:32 +0200
  From: Q. Werty [EMAIL PROTECTED]
  Reply-To: Tomcat Users List [EMAIL PROTECTED]
  To: [utf-8] tomcat-user [EMAIL PROTECTED]
  Subject: Context management and virtual host
 
  I'am looking for a way to manage all contexts installed on
my
  server.
  I've got numerous virtual hosts and I'like NOT to install
  manager context in all virtual hosts. How can I do?
  - Is it possible to install a cross-host context in
Tomcat?
  - I saw the administration interface in Tomcat 4.1 beta.
It's a
  very great work, this interface enable to see/add/remove all
  contexts accross all virtual hosts. I thought it was what I
was
  looking for but apparently there's nothing to
start/stop/reload
  context. Is it planned for final version?
 
  Thanks in advance for any response
 
  Accédez au courrier électronique de La Poste :
www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68
13 50 (0,34€/mn)
 
 
 
 
  --
  To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
  For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]
 
 


 --
 To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]



Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 
€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: Context management and virtual host

2002-08-26 Thread Andrew Conrad

Use the Remote Address Valve

Context path=/manager 
Valve className=org.apache.catalina.valves.RemoteAddrValve
allow=127.0.0.1 /
/Context

More info is here -
http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/valve.html

- Andrew

 -Original Message-
 From: Q. Werty [mailto:[EMAIL PROTECTED]] 
 Sent: Monday, August 26, 2002 11:48 AM
 To: tomcat-user
 Subject: Re: Context management and virtual host
 
 
 I agree there's no problem with installing the manager 
 application in each virtual host. I just don't want to do this  
 because I don't want to publish this context to anyone, even 
 with credentials.
 I would be ready to this on our production server if I could 
 restrict manager context access to some IP adresses (127.0.0.1 
 for exemple).
 == Is it possible? (if not, what about thinking of this in 
 future release?)
 
 
 
  There is no current support for a manager webapp that works
 cross-host.
  The people I know using multiple virtual hosts haven't had
 any problems
  with the notion of installing manager in each host (usually
 with a unique
  username/password if you allow the virtual host users to
 manage their own
  webapps).
  
  Admin webapp support for contexts is primarily for tweaking
 existing
  config properties.  I view manager as the standard mechanism
 for dynamic
  starting and stopping of webapps, in addition to deploying,
 undeploying,
  and reloading.  Although the user interface of manager is
 quite limited,
  it is expressly designed to be used by tools -- such as the
 Ant custom
  tasks included in Tomcat 4.1, and the version of deploytool
 shipped with
  the JWSDP http://java.sun.com/webservices/.
  
  People building plugins for IDEs should really be integrating
 support for
  manager commands instead of trying to embed Tomcat inside
 their
  environments.  They'd find it a lot easier.
  
  Craig
  
  
  On Mon, 26 Aug 2002, Q. Werty wrote:
  
   Date: Mon, 26 Aug 2002 16:42:32 +0200
   From: Q. Werty [EMAIL PROTECTED]
   Reply-To: Tomcat Users List [EMAIL PROTECTED]
   To: [utf-8] tomcat-user [EMAIL PROTECTED]
   Subject: Context management and virtual host
  
   I'am looking for a way to manage all contexts installed on
 my
   server.
   I've got numerous virtual hosts and I'like NOT to install manager 
   context in all virtual hosts. How can I do?
   - Is it possible to install a cross-host context in
 Tomcat?
   - I saw the administration interface in Tomcat 4.1 beta.
 It's a
   very great work, this interface enable to see/add/remove all 
   contexts accross all virtual hosts. I thought it was what I
 was
   looking for but apparently there's nothing to
 start/stop/reload
   context. Is it planned for final version?
  
   Thanks in advance for any response
  
   Accédez au courrier électronique de La Poste :
 www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68 
 13 50 (0,34€/mn)
  
  
  
  
   --
   To unsubscribe, e-mail:   mailto:tomcat-user-
 [EMAIL PROTECTED]
   For additional commands, e-mail: mailto:tomcat-user-
 [EMAIL PROTECTED]
  
  
  
  
  --
  To unsubscribe, e-mail:   mailto:tomcat-user-
 [EMAIL PROTECTED]
  For additional commands, e-mail: mailto:tomcat-user-
 [EMAIL PROTECTED]
  
  
 
 Accédez au courrier électronique de La Poste : 
 www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn)  ; tél : 08 92 
 68 13 50 (0,34€/mn)
 
 
 
 
 --
 To unsubscribe, e-mail:   
 mailto:tomcat-user- [EMAIL PROTECTED]
 For 
 additional commands, 
 e-mail: mailto:[EMAIL PROTECTED]
 


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Context management and virtual host

2002-08-26 Thread Craig R. McClanahan



On Mon, 26 Aug 2002, Q. Werty wrote:

 Date: Mon, 26 Aug 2002 17:48:10 +0200
 From: Q. Werty [EMAIL PROTECTED]
 Reply-To: Tomcat Users List [EMAIL PROTECTED]
 To: [utf-8] tomcat-user [EMAIL PROTECTED]
 Subject: Re: Context management and virtual host

 I agree there's no problem with installing the manager
 application in each virtual host. I just don't want to do this
 because I don't want to publish this context to anyone, even
 with credentials.
 I would be ready to this on our production server if I could
 restrict manager context access to some IP adresses (127.0.0.1
 for exemple).
 == Is it possible? (if not, what about thinking of this in
 future release?)


Check out the Request Filters section on:

  http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/context.html

Craig




  There is no current support for a manager webapp that works
 cross-host.
  The people I know using multiple virtual hosts haven't had
 any problems
  with the notion of installing manager in each host (usually
 with a unique
  username/password if you allow the virtual host users to
 manage their own
  webapps).
 
  Admin webapp support for contexts is primarily for tweaking
 existing
  config properties.  I view manager as the standard mechanism
 for dynamic
  starting and stopping of webapps, in addition to deploying,
 undeploying,
  and reloading.  Although the user interface of manager is
 quite limited,
  it is expressly designed to be used by tools -- such as the
 Ant custom
  tasks included in Tomcat 4.1, and the version of deploytool
 shipped with
  the JWSDP http://java.sun.com/webservices/.
 
  People building plugins for IDEs should really be integrating
 support for
  manager commands instead of trying to embed Tomcat inside
 their
  environments.  They'd find it a lot easier.
 
  Craig
 
 
  On Mon, 26 Aug 2002, Q. Werty wrote:
 
   Date: Mon, 26 Aug 2002 16:42:32 +0200
   From: Q. Werty [EMAIL PROTECTED]
   Reply-To: Tomcat Users List [EMAIL PROTECTED]
   To: [utf-8] tomcat-user [EMAIL PROTECTED]
   Subject: Context management and virtual host
  
   I'am looking for a way to manage all contexts installed on
 my
   server.
   I've got numerous virtual hosts and I'like NOT to install
   manager context in all virtual hosts. How can I do?
   - Is it possible to install a cross-host context in
 Tomcat?
   - I saw the administration interface in Tomcat 4.1 beta.
 It's a
   very great work, this interface enable to see/add/remove all
   contexts accross all virtual hosts. I thought it was what I
 was
   looking for but apparently there's nothing to
 start/stop/reload
   context. Is it planned for final version?
  
   Thanks in advance for any response
  
   Accédez au courrier électronique de La Poste :
 www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68
 13 50 (0,34€/mn)
  
  
  
  
   --
   To unsubscribe, e-mail:   mailto:tomcat-user-
 [EMAIL PROTECTED]
   For additional commands, e-mail: mailto:tomcat-user-
 [EMAIL PROTECTED]
  
  
 
 
  --
  To unsubscribe, e-mail:   mailto:tomcat-user-
 [EMAIL PROTECTED]
  For additional commands, e-mail: mailto:tomcat-user-
 [EMAIL PROTECTED]
 
 

 Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET 
(0,13 €/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




 --
 To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:[EMAIL PROTECTED]




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




RE: Context management and virtual host

2002-08-26 Thread Q. Werty

OK, I haven't saw this. Thanks a lot

 Use the Remote Address Valve

 Context path=/manager 
   Valve
className=org.apache.catalina.valves.RemoteAddrValve
 allow=127.0.0.1 /
 /Context

 More info is here -
 http://jakarta.apache.org/tomcat/tomcat-4.0-
doc/config/valve.html

 - Andrew

  -Original Message-
  From: Q. Werty [mailto:[EMAIL PROTECTED]]
  Sent: Monday, August 26, 2002 11:48 AM
  To: tomcat-user
  Subject: Re: Context management and virtual host
 
 
  I agree there's no problem with installing the manager
  application in each virtual host. I just don't want to do
this
  because I don't want to publish this context to anyone,
even
  with credentials.
  I would be ready to this on our production server if I
could
  restrict manager context access to some IP adresses
(127.0.0.1
  for exemple).
  == Is it possible? (if not, what about thinking of this in
  future release?)
 
 
 
   There is no current support for a manager webapp that
works
  cross-host.
   The people I know using multiple virtual hosts haven't had
  any problems
   with the notion of installing manager in each host
(usually
  with a unique
   username/password if you allow the virtual host users to
  manage their own
   webapps).
  
   Admin webapp support for contexts is primarily for
tweaking
  existing
   config properties.  I view manager as the standard
mechanism
  for dynamic
   starting and stopping of webapps, in addition to
deploying,
  undeploying,
   and reloading.  Although the user interface of manager
is
  quite limited,
   it is expressly designed to be used by tools -- such as
the
  Ant custom
   tasks included in Tomcat 4.1, and the version of
deploytool
  shipped with
   the JWSDP http://java.sun.com/webservices/.
  
   People building plugins for IDEs should really be
integrating
  support for
   manager commands instead of trying to embed Tomcat inside
  their
   environments.  They'd find it a lot easier.
  
   Craig
  
  
   On Mon, 26 Aug 2002, Q. Werty wrote:
  
Date: Mon, 26 Aug 2002 16:42:32 +0200
From: Q. Werty [EMAIL PROTECTED]
Reply-To: Tomcat Users List tomcat-
[EMAIL PROTECTED]
To: [utf-8] tomcat-user tomcat-
[EMAIL PROTECTED]
Subject: Context management and virtual host
   
I'am looking for a way to manage all contexts installed
on
  my
server.
I've got numerous virtual hosts and I'like NOT to
install manager
context in all virtual hosts. How can I do?
- Is it possible to install a cross-host context in
  Tomcat?
- I saw the administration interface in Tomcat 4.1 beta.
  It's a
very great work, this interface enable to
see/add/remove all
contexts accross all virtual hosts. I thought it was
what I
  was
looking for but apparently there's nothing to
  start/stop/reload
context. Is it planned for final version?
   
Thanks in advance for any response
   
Accédez au courrier électronique de La Poste :
  www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92
68
  13 50 (0,34€/mn)
   
   
   
   
--
To unsubscribe, e-mail:   mailto:tomcat-user-
  [EMAIL PROTECTED]
For additional commands, e-mail: mailto:tomcat-user-
  [EMAIL PROTECTED]
   
   
  
  
   --
   To unsubscribe, e-mail:   mailto:tomcat-user-
  [EMAIL PROTECTED]
   For additional commands, e-mail: mailto:tomcat-user-
  [EMAIL PROTECTED]
  
  
 
  Accédez au courrier électronique de La Poste :
  www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn)  ; tél : 08
92
  68 13 50 (0,34€/mn)
 
 
 
 
  --
  To unsubscribe, e-mail:
  mailto:tomcat-user- [EMAIL PROTECTED]
  For
  additional commands,
  e-mail: mailto:[EMAIL PROTECTED]
 


 --
 To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]



Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 
€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Context management and virtual host

2002-08-26 Thread Q. Werty

OK, thanks a lot too.



 On Mon, 26 Aug 2002, Q. Werty wrote:

  Date: Mon, 26 Aug 2002 17:48:10 +0200
  From: Q. Werty [EMAIL PROTECTED]
  Reply-To: Tomcat Users List [EMAIL PROTECTED]
  To: [utf-8] tomcat-user [EMAIL PROTECTED]
  Subject: Re: Context management and virtual host
 
  I agree there's no problem with installing the manager
  application in each virtual host. I just don't want to do
this
  because I don't want to publish this context to anyone, even
  with credentials.
  I would be ready to this on our production server if I could
  restrict manager context access to some IP adresses
(127.0.0.1
  for exemple).
  == Is it possible? (if not, what about thinking of this in
  future release?)
 

 Check out the Request Filters section on:

   http://jakarta.apache.org/tomcat/tomcat-4.1-
doc/config/context.html

 Craig


 
 
   There is no current support for a manager webapp that
works
  cross-host.
   The people I know using multiple virtual hosts haven't had
  any problems
   with the notion of installing manager in each host
(usually
  with a unique
   username/password if you allow the virtual host users to
  manage their own
   webapps).
  
   Admin webapp support for contexts is primarily for
tweaking
  existing
   config properties.  I view manager as the standard
mechanism
  for dynamic
   starting and stopping of webapps, in addition to
deploying,
  undeploying,
   and reloading.  Although the user interface of manager
is
  quite limited,
   it is expressly designed to be used by tools -- such as
the
  Ant custom
   tasks included in Tomcat 4.1, and the version of
deploytool
  shipped with
   the JWSDP http://java.sun.com/webservices/.
  
   People building plugins for IDEs should really be
integrating
  support for
   manager commands instead of trying to embed Tomcat inside
  their
   environments.  They'd find it a lot easier.
  
   Craig
  
  
   On Mon, 26 Aug 2002, Q. Werty wrote:
  
Date: Mon, 26 Aug 2002 16:42:32 +0200
From: Q. Werty [EMAIL PROTECTED]
Reply-To: Tomcat Users List tomcat-
[EMAIL PROTECTED]
To: [utf-8] tomcat-user tomcat-
[EMAIL PROTECTED]
Subject: Context management and virtual host
   
I'am looking for a way to manage all contexts installed
on
  my
server.
I've got numerous virtual hosts and I'like NOT to
install
manager context in all virtual hosts. How can I do?
- Is it possible to install a cross-host context in
  Tomcat?
- I saw the administration interface in Tomcat 4.1 beta.
  It's a
very great work, this interface enable to
see/add/remove all
contexts accross all virtual hosts. I thought it was
what I
  was
looking for but apparently there's nothing to
  start/stop/reload
context. Is it planned for final version?
   
Thanks in advance for any response
   
Accédez au courrier électronique de La Poste :
  www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92
68
  13 50 (0,34€/mn)
   
   
   
   
--
To unsubscribe, e-mail:   mailto:tomcat-user-
  [EMAIL PROTECTED]
For additional commands, e-mail: mailto:tomcat-user-
  [EMAIL PROTECTED]
   
   
  
  
   --
   To unsubscribe, e-mail:   mailto:tomcat-user-
  [EMAIL PROTECTED]
   For additional commands, e-mail: mailto:tomcat-user-
  [EMAIL PROTECTED]
  
  
 
  Accédez au courrier électronique de La Poste :
www.laposte.net ; 3615 LAPOSTENET (0,13 €/mn) ; tél : 08 92 68
13 50 (0,34€/mn)
 
 
 
 
  --
  To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
  For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]
 
 


 --
 To unsubscribe, e-mail:   mailto:tomcat-user-
[EMAIL PROTECTED]
 For additional commands, e-mail: mailto:tomcat-user-
[EMAIL PROTECTED]



Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 
€/mn) ; tél : 08 92 68 13 50 (0,34€/mn)




--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]