"scott.stark(a)jboss.org" wrote : | We don't need to force the use of jaxb. Just have an AttachmentSerializer for ServiceDeployment that deals with its issues. If you already have a jaxb variation working, great. Well let's say partly - at the moment it is required to leave the initial parsing as it is. Otherwise things like nested mbeans would get lost. The flattened metadata then can be marshalled/unmarshalled with the JAXBAttachmentSerializer. So doing that with the conf/jboss-service.xml looks quite ok, but there are still some things missing and this of course needs some testing. I committed the things i have for the ManagedConnectionFactoryDeploymentGroup. So the attachment of the updated datasource is now persisted in xml. Basically all tests in the profileservice target there are passing except: org.jboss.test.profileservice.test.SecurityManagedObjectsTestCase, which also fails on hudson. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4188919#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...