"debarcar" wrote : Hi Dimitris, | It seems the solution is better than my expectation. And I have two following questions: | | 1) If I add a new MBean, such as add a new Destination in JMS, can this solution store the new one for me? | 2) It seems the persistence function is only for the Model MBeans, can I let it also support the common MBeans? |
1) If you add it through the jmx-console, there will be no xml descriptor in deploy and your service will not be persistent. You'll have to generate the mbean+xmbean descriptor and copy it to the deploy directory to have a truly persistent service (i.e. make a "factory" MBean service of yours). We, too, are thinking of creating somekind of descriptor factory for common services to achieve exactly this, but it still in the works. 2) You can use an XMBean descriptor to "wrap" as ModelMBean plain old Standard MBeans. For example, if you look at the JNDIView service, started from conf/jboss-service.xml, this used to be a plain Service MBean, but at some point an XMBean wrapper was added, so that useful metadata description could be displayed through the jmx-console. Regards /Dimitris View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3846864#3846864 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3846864 ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
