"scott.stark(a)jboss.org" wrote : The jbossxb methods taking a SchemaResolver used by SchemaResolverDeployer do not take an existing root(although I don't know why they could not). The reason was that the way to merge two (or more) XML contents into one Java object model wasn't obvious (w/o requiring a user to write the merging code). Of course, we could define some rules to support this. For an example of a non-obvious merging issue, imagine we have ejb-jar.xml and jboss.xml listing a set of beans. How can I get the ejb-jar bean info for a jboss bean info being parsed? We can't rely on the same ordering of bean infos in ejb-jar and jboss.xml (they can be different and some beans maybe missing from jboss.xml or bean infos from ejb-jar could be collected into a java.util.Set and iteration order would be different). This can only be done by ejb-name. In this case, the user would have to provide some merging logic (writting custom element handlers, probably). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976761#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...