Henri Gomez wrote: >> 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.
Of course not. But the JMX API should be available to your application. You can include it in WEB-INF for each app - but then what do you do, have one HTTP adaptor ( or SNMP adaptor ) for each app ? In a multi-app env, each app can be JMX-enabled ( and have it's own domain ). It is the servlet engine ( or a module in the servlet engine ) that must isolate the webapps - since JMX itself has no idea or knowledge about the container. But nothng else - the container should just make sure the jmx is available and the apps are isolated and the security settings are right. -- Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
