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
which would then get added to the MC deployment's MBean.
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.