I wouldn't say it's a similar issue. It depends on what you want to do but SingletonSchemaResolverFactory may not be a good choice for this feature. It's singleton, so it's one for all. While, theoretically, different JARs may use different classes for the same namespace. In this case, component-specific configuration shouldn't modify global configuration. Instead, there should be a JAR-specific SchemaBindingResolver which would delegate to the SingletonSchemaResolverFactory (or whatever the global resolver is) in case it can't resolve the binding by itself. If bindings from different JARs don't and can't contradict each other then no problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223134#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...