It is now just as easy to use xmbeans as standard mbeans in jboss + xdoclet. I've converted the 2 mbeans in transaction to xmbeans. The xml descriptors are generated from markup by xdoclet.
The service.xml is almost generated by xdoclet as well: the config for these two mbeans is generated, but due to insufficiently explicit dependency tracking the config has to be in the transaction-service.xml file with some mbeans from other packages. Finally, the jmx-console now also shows the description of all elements: these descriptions originated in the xdoclet markup in the source code. The main change needed outside of transaction was to make the ModelMBeanInvoker forward MBeanRegistration lifecycle calls to the managed resource if that resource implements MBeanRegistration. I haven't checked the jmx spec to see if it has opinions on this. Thanks david jencks ------------------------------------------------------- Sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
