In addition to my questinos below, is mbeans-descriptors.xml a Tomcat-specific file or part of JMX in general? I can't tell - it seems to appear in links like the following:
http://commons.apache.org/modeler/apidocs/org/apache/commons/modeler/package-summary.html But its DTD is under commons.apache.org - so is this specific to an Apache JMX implementation, part of JMX, or something else? lightbulb432 wrote: > > The following link describes using JMX with Tomcat. Step #4 talks about > the mbeans-descriptors.xml file, but it seems to make no difference when > using it. If I don't include elements in that file that I do in MBean > interface, it still works in JConsole properly - and the descriptions > entered don't seem to show up in JConsole either. > > http://oss.wxnet.org/mbeans.html > > Also, things like the "writeable" property and the "type" property that > are specified in this file could easily be determined from the MBean > interface, from return types, whether a getter has a corresponding setter, > etc. Then what is the use of this file if updating it to keep in sync with > the MBean interface makes no difference? Is it necessary to begin with? > > Thanks. > > > > > lightbulb432 wrote: >> >> How, from a web application deployed to Tomcat, can you customize the >> behavior of your web application based on attributes specified in an >> MBean? The link http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html >> talks a lot about Ant tasks, but that's not really what I'm looking to >> do. >> >> How can you get programmatic access to MBeans? And how do you deploy >> MBeans to Tomcat? >> >> I'm pretty confused here...hopefully someone can clarify. Thanks. >> > > -- View this message in context: http://www.nabble.com/Use-JMX-to-manage-applications-tf3978363.html#a12319486 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
