tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Anderson <>
Subject RE: Tomcat Admin Web Interface
Date Thu, 14 Jun 2001 21:10:28 GMT
Count me in on working on an admin interface for Tomcat.  This along with a
better install/connector config program would go a long way to improve the
overall usability of Tomcat for me.

Having had experience working on server product GUIs, the plan to decide
what goes into the GUI before starting the project is definitely the best
way to go.  Even though there is a considerable amount of planning and
discussion that goes into the GUI requirements sheet, in the end it is
easier to deny unreasonable requests like, "we have this new functionality
two weeks before the release can you incorporate it into the admin
interface?", or "I'd like the GUI to wash and wax my car."  A hard and fast
list of GUI features for each release is essential to keeping the GUI
project manageable

My 2 cents.


On Thu, 14 Jun 2001, M B wrote:

> Hello All,
> In response to the recent postings regarding Tomcat
> documentation and administration (Re: ~rant~ Docs,
> user list, etc.), I am willing to contribute much
> effort in this area.  In addition to documentation, I
> am particularly interested in helping to build an
> administrative web interface for Tomcat 4.0, something
> similar to JRun Management Console, for example.

That would be awesome!

> Naturally, I want to coordinate my efforts with the
> Tomcat community.  Can anyone please point out where I
> should begin, or who I should contact?  Is there a
> project for this?  The Catalina TODO identifies John
> Shin as volunteer for producing an admin interface,
> but I thought I should email this list before
> contacting him directly.  

He volunteered long, long, ago but I haven't heard anything from him

As it happens, I've been accumulating a list of functional requirements
for admin capabilities that I'd like to post for discussion.  I'll be
finished with what I'm thinking in the next couple of days.

What I'd like to see us do on issues like this is to discuss and agree on
a functional specs document that is checked in to the CVS repository, and
then start working together on the pieces.  It's a little more formal than
the usual :-) open source approach, but I think it will help in the long
run.  Does that sound like a useful plan?

> Thanks,
> Matt


View raw message