[jboss-dev-forums] [Design of JBossXB] - Too much resolution?

I seem to be seeing many more of these debug msgs currently running the metadata tests: anonymous wrote : | 18:07:14,709 DEBUG [JBossEntityResolver] Cannot resolve [publicID=http://www.jboss.com/xml/ns/javaee,systemID=null] | 18:07:15,360 DEBUG [JBossEntityResolver] Cannot resolve [publicID=null,systemID=http://www.jboss.com/xml/ns/javaee] | 18:07:15,360 DEBUG [JBossEntityResolver] Cannot resolve [publicID=http://www.jboss.com/xml/ns/javaee,systemID=null] | 18:07:15,813 DEBUG [JBossEntityResolver] Cannot resolve [publicID=null,systemID=http://www.jboss.com/xml/ns/javaee] | 18:07:15,814 DEBUG [JBossEntityResolver] Cannot resolve [publicID=http://www.jboss.com/xml/ns/javaee,systemID=null] | 18:07:16,020 DEBUG [JBossEntityResolver] Cannot resolve [publicID=null,systemID=http://www.jboss.com/xml/ns/javaee] | 18:07:16,020 DEBUG [JBossEntityResolver] Cannot resolve [publicID=http://www.jboss.com/xml/ns/javaee,systemID=null] | The majority seem to be coming from this code, triggered by elements like proxy-factory-config: | if(resolver != null) | { | // this is wildcard handling | String schemaLocation = attrs == null ? null : Util.getSchemaLocation(attrs, qName.getNamespaceURI()); | SchemaBinding schema = resolver.resolve(qName.getNamespaceURI(), null, schemaLocation); | if(schema != null) | { | element = schema.getElement(qName); | } | } | Is there a way to improve this? Its really slowing down the tests. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4095059#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...