[jboss-dev-forums] [Design of Management Features on JBoss] - Re: Use of JBAS5 management api's by user apps

[scott.stark@jboss.org]

"charles.crouch at jboss.com" wrote : So only spec defined metadata is managable for things like .wars and .ears because those are the only things the which the .war and .ear deployers knows about?
  | 
Yes. An aspect overrides the deployment metadata to incorporate the management changes.

"charles.crouch at jboss.com" wrote : 
  | So if you wanted to add support for non-spec defined metadata you would need to write another deployer?
That is not going to help as deployers run off of the deployment metadata attachments. If it was an mc bean property, or jmx mbean property that controlled the frequency, it would already be managable via the corresponding component deployer.

So, if you make your configuration object an mc mbean, and then inject it, you would have a managable configuration object. We should allow injection of mc beans into ee components via an @Resource(...) annotation.

Otherwise, you would have to replicate behavior the profile service/deployers perform for deployment metadata.


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

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