On Fri, 15 Jun 2001, Morrison, John wrote:
> Would/could this be implemented as a web context with (possibly) some
> 'administration' flag set in it's context that way, if you didn't want to
> have a GUI (security?) you could just remove the context?
>
My thinking to date has been that we should support multiple faces
(webapp, SOAP-based, perhaps Jini and/or RMI) that talks to the same
"business logic" underneath, so that people could choose different
integration approaches to meet their needs.
WRT shipping as a webapp, the current Tomcat 4 "manager" application is
shipped with a security constraint that requires role "manager", but there
are no such users in the default usernames database (i.e. you have to
explicitly add one). If we trust container-managed security, I don't see
much need for a separate "administrative application" flag in the
configuration.
> Just my 2p worth ;)
>
Craig
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, 14 June 2001 23:13
> To: '[EMAIL PROTECTED]'
> Subject: RE: Tomcat Admin Web Interface
>
>
>
> It would be very good at this stage to go back 1 1/2 years in tomcat
> archives and re-read the "admin" thread. It was a huge discussion, with
> many ideas - but nothing happened.
>
> As usual, my opinion is that you should start with a prototype and/or
> existing code - and figure out what is the best way to do it by trying
> different aproaches.
>
> Costin
>
>
>
>
> On Thu, 14 Jun 2001, Eric Anderson wrote:
>
> > 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.
> >
> > Eric
> >
> >
> > 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
> > lately.
> >
> > 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
> > >
> >
> > Craig
> >
>
>
> =======================================================================
> Information in this email and any attachments are confidential, and may
> not be copied or used by anyone other than the addressee, nor disclosed
> to any third party without our permission. There is no intention to
> create any legally binding contract or other commitment through the use
> of this email.
>
> Experian Limited (registration number 653331).
> Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF
>
