Scott M Stark wrote:
Well, if you want to add an indirection, then it's easy. Tomcat 5 support all those monitoring features using JavaBean properties + the Jakarta Commons Modeler and its introspection mechanism. So the wrapper is also an MBean, and its properties, including the JSR 77 statistics, are accessible either through JMX, or as normal Java properties.That is the issue. I would rather the web container not directly create the JSR77 Servlet model. Instead it should create its own management facade that is used by the JBoss JSR77 layer to present the Servlet model mbean with the correct naming structure. So there justs needs to be some way to specify the root structure of the web container JMX names to avoid conflicts. Say the JMX domain and a list of properties that should be included in a given war web context.
Remy
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
