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

"charles.crouch(a)jboss.com" wrote : | a) Have we approached the JBoss Messaging team about including these annotations on their classes | No, we were using it as a typical example of introducing admin to an external project. We should not have to annotate the beans to manage them. "charles.crouch(a)jboss.com" wrote : | b) Can we supply our own version of org.jboss.jms.server.destination.QueueService which acts as a proxy and does include the annotations. | Yes, we originally did that but it was more cumbersome in terms of taking existing messaging destination deployments and making them manageable. "charles.crouch(a)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. I'll create an issue and ask Ales to look at the metadata repository approach. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4191065#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...