I think there are 2 types of definition for this and 2 types of deployment
Let's look at the 2 types of definition: * One is, the introduction obtains the management interface in a generic way. * The other is the introduction obtains the management interface (and metadata) through other annotations. The two types of deployment * The class is just tagged as @Mbean(). MBean instances are defined and deployed through regular XML * The class is tagged with @MBean(objectName="jboss:service=Foo"). In this case, the deployer will iterate through all class files in the deployment looking for classes tagged with @MBean and that have an objectName defined. These will be deployed directly into JMX and XML is not needed to deploy these services. We should have a similar @Bean annotation that automatically deploys a class into the JBoss kernel/pojo container. Bill View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861110#3861110 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861110 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
