[Design the new POJO MicroContainer] - Why SingletonSchemaResolverFactory?
by scott.stark@jboss.org
Why is the BasicXMLDeployer using the SingletonSchemaResolverFactory? This cannot be extended and does not allow one to add new schemas without modifying the existing private ctor, which mean modifying the jbossxb release:
| private SingletonSchemaResolverFactory()
| {
| addSchema("urn:jboss:aop-beans:1.0", "org.jboss.aop.microcontainer.beans.xml.AOPBeansSchemaInitializer", Boolean.FALSE);
| addSchema("urn:jboss:bean-deployer", "org.jboss.kernel.plugins.deployment.xml.BeanSchemaInitializer", Boolean.FALSE);
| addSchema("urn:jboss:bean-deployer:2.0", "org.jboss.kernel.plugins.deployment.xml.BeanSchemaInitializer20", Boolean.FALSE);
| addSchema("urn:jboss:javabean:1.0", "org.jboss.kernel.plugins.config.xml.JavaBeanSchemaInitializer", Boolean.FALSE);
| }
|
Either this should be subclassable, the mutator methods public, or BasicXMLDeployer using a different resolver factory.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002570#4002570
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002570
19 years, 2 months