Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 24183 invoked from network); 7 Feb 2002 21:18:45 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 7 Feb 2002 21:18:45 -0000 Received: (qmail 25378 invoked by uid 97); 7 Feb 2002 21:18:41 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 25343 invoked by uid 97); 7 Feb 2002 21:18:40 -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 25326 invoked from network); 7 Feb 2002 21:18:40 -0000 Date: Thu, 7 Feb 2002 13:18:34 -0800 (PST) From: "Craig R. McClanahan" To: Tomcat Developers List Subject: Re: MBeans dev In-Reply-To: <20020207201459.10278.qmail@hm36.locaweb.com.br> Message-ID: <20020207130444.V68704-100000@icarus.apache.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: localhost 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 Thu, 7 Feb 2002, Renato wrote: > Date: Thu, 7 Feb 2002 18:14:59 > From: Renato > Reply-To: Tomcat Developers List > To: tomcat-dev@jakarta.apache.org > Subject: MBeans dev > > Hi all, > > I've seen a lot of development regarding MBean lately and I'm a little lost > about what are the new functionality that Catalina will have. Could > somebody explain what MBean are ( and for what they are useful ) or give > some directives, where I can read about ? ( I know there is plenty of > material about Message Beans in J2EE but I imagine these MBeans for Tomcat > are somehow different, aren't they ? ) > The "MBean" that is referred to here is a "managed bean" from the Java Management Extensions (JMX) APIs. You can read about it (and get the spec) from . The basic idea is that each component object within Catalina (Engine, Host, Context, Valve, Logger, Realm, and so on) has a corresponding MBean through which it can be created, configured, and removed on-the-fly. In addition, the JMX APIs have the notion of being able to save the configuration state in such a way that it can be reused the next time you start up the server. For Tomcat, we're using the JMX APIs in the administration webapp that will, when it's done, let you never have to touch the server.xml file again -- all of the configuration can be done interactively through a tool. The fact that we're doing it all through MBeans also means that managing a Tomcat 4 instance can also be easily built in to any other management tool that knows how to speak JMX. > Thanks for the patience > Renato. > Craig McClanahan -- To unsubscribe, e-mail: For additional commands, e-mail: