Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: Wed, 07 Jan 2004 00:33:38 +0900
From: TANAKA Yoshihiro <tomcatdev@ytp.ne.jp>
To: tomcat-dev@jakarta.apache.org
Subject: Re: [PATCH]Virtual Host Choice on HTML Manager
In-Reply-To: <3FF9C1A8.9070401@apache.org>
References: <20040105194511.GA11678@gkar.earthdome.org>
 <3FF9C1A8.9070401@apache.org>
Message-Id: <20040107000140.AE5D.TOMCATDEV@ytp.ne.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

on Mon, 05 Jan 2004 20:57:28 +0100
Remy Maucherat <remm@apache.org> wrote:

>> An acceptable patch would be to extend the existing manager class with
>> a new class which implements this "feature".  Then those administering
>> Tomcat can choose which version of the manager they want to install.
>
>I agree with this.
>Is one manager per vhost really too much to ask ? (since different 
>principals will be needed in many situations)

Thanx for your comments everyone. I got your point.
I'm not lazy to login each virtual host, but I am 
when installing manager application to each virtual host.

>There are a use cases for the feature, of course, so I'm ok with having 
>an extension class that could replace the default manager servlet.

I'll try to modify as follows:

1)Make new classes extend HTMLManagerServlet & ManagerServlet.
2)These servlets are optional. (commented out in web.xml)
3)Only admin role can access them. (by web.xml)

Do you think I've it figured out?

Regards.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org