Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 77074 invoked from network); 13 Feb 2002 02:10:25 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 13 Feb 2002 02:10:25 -0000 Received: (qmail 8801 invoked by uid 97); 13 Feb 2002 02:10:24 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 8785 invoked by uid 97); 13 Feb 2002 02:10:23 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 8774 invoked from network); 13 Feb 2002 02:10:23 -0000 Message-ID: <01aa01c1b433$b2568170$6501a8c0@apache.org> From: "Remy Maucherat" To: "Tomcat Developers List" References: <20020212180102.C67363-100000@icarus.apache.org> Subject: Re: JMX Support in Tomcat 4 Date: Tue, 12 Feb 2002 18:11:02 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: localhost.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > On Tue, 12 Feb 2002, Remy Maucherat wrote: > > > What could be done is maybe to write a (complex) tag library, which would > > ease the process of writing admin pages which would manipulate MBeans. Of > > course, that's quite a bit harder than writing custom admin pages, so I can > > understand the rationale behind that from a dev schedule standpoint ;-) > > > > To get such a tag library started, there's an "attribute" tag in the admin > webapp (HEAD branch) that displays a named attribute from a named MBean. > It would certainly make sense to abstract this out into a general MBean > manipulation tag library (perhaps in jakarta-taglibs?). Yes, that would be a good starting point. The taglib is IMO the only satisfactory solution, as the application needs to be able to decide of the LnF of the admin app, as well as how the beans should be organized / presented (for example, the Tomcat admin webapp uses a tree, but other applications may do something different altogether). The only problem is that a significant part of the development would still need to be done by the application (it's not a "your HTML admin interface in 5 mins" type of deal). jakarta-taglibs looks like the right home for this, but I'd like to hear from Carlos to know how he plans to implement it. Remy -- To unsubscribe, e-mail: For additional commands, e-mail: