tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brad Cox <>
Subject Re: tomcat gui
Date Mon, 02 Jul 2001 15:39:34 GMT
At 8:15 AM -0700 7/2/01, <> wrote:
>The "right" thing is to use a 2-layer architecture, with the backend
>beeing a set of servlets/jsps in /admin, with minimal ( or no ) GUI. The
>frontend can be a swing GUI, a webapp ( that can run on a different
>container and manage a set of tomcat instances ), or a module part of one
>of the existing admin GUIs.

Wouldn't this mean that the GUI would be ussless until the things 
tomcat depends on (apache to some extent (port 8080 conflicts), 
connectors, classloaders, jar files) are all exactly right?

In my experience, these are precisely the things that most often go 
wrong and generate the most obscure errors. By this reasoning, the 
GUI should concentrate on these things first and avoid relying on 
tomcat-based functionality until the fundamentals are known to be 

PS: Building Java GUIs is straightforward given Visual Age or simlar. 
The hard part is understanding what tomcat needs to get on its feet 
and building this understanding into a GUI, either by implementing it 
independently or by catching and reporting exceptions thrown by 
existing tomcat code.
For industrial age goods there were checks and credit cards.
For everything else there is mybank.dom at
Brad Cox, PhD; 703 361 4751

View raw message