[jboss-dev-forums] [Design of Management Features on JBoss] - ManagedObjects for MBeans

[ips]

I noticed that the variouus types of jboss.web MBeans are all exposed as ManagedComponents with type ComponentType{type=MBean, subtype=Web}. For example, my AS5 instance has the following ManagedComponents:

org.jboss.managed.plugins.ManagedComponentImpl at 17498cb{name=jboss.web:host=127.0.0.1,type=Host, type=ComponentType{type=MBean, subtype=Web}, owner=ManagedDeployment at 23354564}

org.jboss.managed.plugins.ManagedComponentImpl at ca251{name=jboss.web:name=http-127.0.0.1-8080,type=GlobalRequestProcessor, type=ComponentType{type=MBean, subtype=Web}, owner=ManagedDeployment at 23354564}

org.jboss.managed.plugins.ManagedComponentImpl at 1babf49{name=jboss.web:name=http-127.0.0.1-8080,type=ThreadPool, type=ComponentType{type=MBean, subtype=Web}, owner=ManagedDeployment at 23354564}

It would be more intuitive if each of the different types of jboss.web MBeans were exposed as a different type of ManagedComponent, e.g.:

ComponentType{type=MBean, subtype=Web:Host}
ComponentType{type=MBean, subtype=Web:GlobalRequestProcessor}
ComponentType{type=MBean, subtype=Web:ThreadPool}

That way, in the Jopr jboss-as-5 plugin, each component type can be mapped one-to-one to an RHQ ResourceType. Otherwise, we would have to parse the component names to figure out which type of jboss.web MBean we are dealing with.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220340#4220340

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220340