Date: 2004-02-15T16:44:29 Editor: 209.181.233.150 <> Wiki: Apache Geronimo Wiki Page: WebConsole URL: http://wiki.apache.org/geronimo/WebConsole
no comment Change Log: ------------------------------------------------------------------------------ @@ -1,22 +1,21 @@ The console-web module is a web management interface for the Geronimo server. Its purpose is to provide a lightweight and intuitive web application which can manage the internal operations of the server, its components and any applications hosted on it. This tool should help Geronimo's core development team and the end users to work with the server. Like the other console efforts, the console-web module makes heavy use of the JMX APIs. -The main components for this module are presently being developed by N. Alex Rupp. The core, extensible portions of the web application will reside in the Geronimo project CVS, and a set of optional plugins for the application will be made available via maven. +At the beginning of February 2004, it was decided that the JSP-driven JMX Debugging Console should be abstracted out of the console-web module and relocated into its own module (see JmxDebuggingTool). Geir Magnusson Jr is heading up the development of this new module, and is using Velocity instead of JSP. Development on the JSP-driven module will most likely continue in a separate project. -At this point in the development of the application, there are two core modules. The first module is a raw JMX management console which is intended for use in both MX4J and Geronimo. The second module in development is an implementation of the JSR-88 Tools API. Several other plugin modules have been discussed and developed. +From this point forward, then, the Console-web module will focus on management of server components in a way that is easy for server admins to understand. The Console-Web module will very likely be developed as a sandbox module, or if that becomes impractical or prohibitive it will be developed somewhere else. -The architecture of the console-web application is still evolving to be more modular and easily extensible. As it develops, more information about it will be placed herein. +The architecture of the Console-Web application is still evolving to be more modular and easily extensible. As it develops, more information about it will be placed here. = Feature List = -(this material is slightly out of date and under revision) +(this material is in a constant state of revision and subject to change) -An extremely basic roadmap for the features of the web client software follows, in order of their relative importance: +An extremely basic roadmap for the features of the console-web module follows, in order of their relative importance: * Implement a method invocation interface for simple methods (those with no input parameters or Strings as input parameters) * Implement support for method invocations which take arrays and primitive data types as input parameters * Build support for complex method invocations (those which require objects returned by other invoked methods as input parameters). This involves the creation of some kind of value stack to store returned parameters, and components to sort and display these components in the console * Only allow methods to be invoked if the required parameters are available - * Output the JSR-77 components in an easy-to-read tree structure * Link return types to API-style documentation * Provide some kind of front end for deployment descriptors * Link Deployment''''''Descriptor references in the attributes table to some sort of file display @@ -26,7 +25,7 @@ * Make the console application-aware = Architectural Goals = -(this material is slightly out of date and under revision) +(this material is in a state of constant revision and subject to change) We're concerned with keeping the web management console flexible and relatively easy to extend. As such, we're trying to implement the following changes to the application's architecture.
