Craig, Thank you for the explanation of that. Very cool deal. The server.xml is pretty ugly to edit manually.
----- Original Message ----- From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Thursday, February 07, 2002 16:18 Subject: Re: MBeans dev > > > On Thu, 7 Feb 2002, Renato wrote: > > > Date: Thu, 7 Feb 2002 18:14:59 > > From: Renato <[EMAIL PROTECTED]> > > Reply-To: Tomcat Developers List <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > 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 <http://java.sun.com/products/JavaManagement>. > > 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: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
