[jboss-dev-forums] [Design of POJO Server] - Re: Why do Topic/Queue descriptors need extra metadata in or

[adrian@jboss.org]

"scott.stark at jboss.org" wrote : 
  | "charles.crouch at jboss.com" wrote : 
  |   | c) Can we supply this annotation as some sort of cross-cutting concern? i.e. all instances of org.jboss.jms.server.destination.QueueService created by the MC need to have this annotation applied. I'm fine with having another *single* deployment descriptor which we would ship with that defines this, as opposed to getting users to update *every* destination descriptor they have.
  |   | 
  | This should be doable via the metadata repository using a loader that adds this annotation for specific mbean types. This could also be done by changing the ServiceMetaDataICF, probably other ways.
  | 

The original idea was that all these factories (ManagedObject/MetaType/MetaValue)
contain overridde mechainsms.
So for example you can add a ManagedObjectBuilder by class to the 
ManagedObjectFactory.

The further idea was that xml definitions for these plugins would be written
which would mean in the jboss-messaging deployment we could add some
xml to define their MO definitions.

This is necessary because although we can ask other jboss projects to annotate
their (m)beans for management, they might refuse, do it wrong or it might not be a
jboss project. So we need a way to retrofit or fix the managed object description.

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

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