> Think about it - each app can expose config and status > data to the mx layer, and the config app ( or another > tool ) can manage not only tomcat, but also each webapp. > JMX is not restricted to server code, it can ( and should) > be used in user apps as well. And that's where things > will be intersting.
As someone who write large web applications, I added JMX support directly into the application, so I'd like to keep control on it, ie creating JMX, JMX HTTP adaptor. I don't think the servlet engine should do it. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
