3 Replies Latest reply on Jun 29, 2006 2:11 PM by starksm64

Adding support for dependencies on jmx kernel beans to the b

starksm64 Jun 27, 2006 1:10 PM

As indicated on this thread:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953785

there is a mismatch in terms of dependencies between the mc beans and the legacy jmx beans that affect integration of the bean deployer in jboss-4.0.x. What would it take to be able to import a jmx kernel bean into the bean deployment kernel such that one could express depenencies on the legacy jmx kernel beans?

1. Re: Adding support for dependencies on jmx kernel beans to t

starksm64 Jun 28, 2006 2:24 PM (in response to starksm64)

A related discussion:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=64876
Actions
2. Re: Adding support for dependencies on jmx kernel beans to t

adrian.brock Jun 29, 2006 7:27 AM (in response to starksm64)
I already discussed this Thomas and you pointed to the
thread where we discussed in more detail.

In the 4.0.4 MC deployer there is no link between beans
and mbeans. It is the deployment (an MBean) that takes
part in jmx dependencies.

The only way to satisfy a dependency would be to add
a "kludge" to the MC deployment descriptor (or use an
alternate dds) that lets you express

<deployment> <jmx-depends>jboss:server=something</jmx-depends>

which would then get added to the MC deployment's MBean.
Actions
3. Re: Adding support for dependencies on jmx kernel beans to t

starksm64 Jun 29, 2006 2:11 PM (in response to starksm64)

Ok, it does not look like this should require a new mc release to be able to augment the BeanSchemaBinding to support this. I'm thinking its just an extended SchemaBinding that has a wrapper root object to combine the mc metadata and adds another namespace and ObjectFactory for the jmx-depends list so as not to introduce non-mc metadata into the BeanSchemaBinding.

http://jira.jboss.com/jira/browse/JBAS-3353
Actions

Go to original post