[jboss-dev-forums] [Design the new POJO MicroContainer] - Re: Why SingletonSchemaResolverFactory?
adrian@jboss.org
do-not-reply at jboss.com
Wed Jan 17 10:46:42 EST 2007
"alesj" wrote : I used this 'hack' to temp add new Spring schema:
|
| | public void setUp() throws Exception
| | {
| | SchemaBindingResolver resolver = SingletonSchemaResolverFactory.getInstance().getSchemaBindingResolver();
| | DefaultSchemaResolver defaultSchemaResolver = (DefaultSchemaResolver) resolver;
| | defaultSchemaResolver.addSchemaInitializer("urn:jboss:spring-beans:2.0", new SpringSchemaInitializer());
| | defaultSchemaResolver.addSchemaLocation("urn:jboss:spring-beans:2.0", "mc-spring-beans_2_0.xsd");
| | super.setUp();
| | }
| |
|
| But I agree with you.
The Spring one (and other known ones) should be added to the singleton.
If the initializer class is not in the classpath, it will ignore it.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002875#4002875
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002875
More information about the jboss-dev-forums
mailing list