[jboss-dev-forums] [Design of POJO Server] - ManagedObjects of ManagedObjects, etc.

[adrian@jboss.org]

Apologies in advance if this is a bit of a brain dump since I don't have
this clear in my head yet.

If you look at the OpenMBean api there is an OpenType, SimpleType.OBJECT_NAME
which is used to link MBeans together, i..e. to implement references.

Currently in the MetaType api I haven't added this.

The main use case for this is for ManagedObjects of ManagedObjects,
e.g. a ServiceDeployment has a LoaderRepositoryConfig and a List
which need to be ManagedObjects in their own write.
This part is fairly trivial to implement.

What is not so trivial is when you get to more complicated deployments.
e.g. an ejb deployment can have multiple attachments (ejb-jar.xml, jboss.xml,
jbosscmp-jdbc.xml)

Additionally, the ejb deployment is made of multiple ejbs, each has the
same split, i.e. multiple attachments but they see the "sub managed objects"
of the main managed objects.

These are obviously references like the SimpleType.OBJECT_NAME.

There are also two views:
1) The merged view, i.e. I am managing this ejb
2) The split view, i.e. give me the updated attachments (plural) for this ejb
deployment

Finally, the keys to these references can be used elsewhere,
e.g. the ejb's assembly descriptor

What is not clear to me yet, is how we implement this such that:
* It is easy for the deployer to describe how these references work
(this element of jboss.xml is related to another element in ejb-jar.xml)
* It is easy for the profile service/admin console to understand/use these references
(e.g. providing a drop down list of available ejb-names when editiing the
assembly descriptor)

I think only going through the more complicated uses cases will reveal
all the issues, unless somebody has a clearer view than me on them?

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

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