&quot;adrian(a)jboss.org&quot; wrote : | It is then simply a case of parsing (using JAXB - or JBossXB with JAXB annotations) | and extracting the metadata into deployment attachments. | The big problem is the embedded MBeans in the -ds.xml file. Like Scott said about namespaces, both JAXB and especially JBossXB (which has even better support) can parse different objects based on the namespace. But in the current -ds.xml the mbean stuff is not in a different namespace and the mbean stuff doesn't have a JAXB or JBossXB based parser. It should be: | <connection-factorties xmlns="urn:jboss-jca:5.0"> | | <!-- Our metadata --> | <connection-factory>...</connection-factory> | | <!-- Somebody else's metadata --> | <mbean xmlns="urn:jboss-jmx:5.0">...</mbean> | | </connection-factories> | This has two solutions: 1) Junk the -ds.xml and move to a -cf.xml which either doesn't support embedded mbeans or does it via a namespace 2) Include a "copy" of the mbean model in the jca namespace. When I say "copy", this could just be some form of bridge/wrapper that updates the real ServiceMetadata objects, it is only there is to fool the xml parser machinery into thinking there is an urn:jboss-jca:5.0:mbean element. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4023702#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...