Craig - I'm not sure where the current naming conventions for mbeans are defined in 4.0, and how 'frozen' they are.
This mail is about the first part of the mbean name - the domain. Curently there are several 'domains' in use: - catalina - used for most catalina objects ( but not sure how this works for per/context modules or users) - realm - used for users/groups Also: - jk ( used by all jk components ) - tomcat3 ( used by tomcat3 interceptors ) - webapp ( used by tomcat3 webapps ) - tomcat3.request ( a very bad way to expose the active requests/threads ) The biggest problem is how do we deal with webapps - it is possible to have modules and realms that are local to a context. Another problem is the 'generic' use of "User" ( and 'type' ) - if catalina is embeded in another app that may easily lead to name conflicts. My proposal would be to use: - 'tomcat' - for all 'server level' components ( including global Realm and User) - one domain per webapplication. The name will be composed of the host/path. In other words, we'll have a domain per classloader. Comments ? Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
