JBXB-206: Performance work

[jesper.pedersen]

To follow up on the JIRA - the code as it stands currently is:

 UnmarshallerFactory unmarshallerFactory = UnmarshallerFactory.newInstance();
 Unmarshaller unmarshaller = unmarshallerFactory.newUnmarshaller();

 MutableSchemaResolver resolver = SingletonSchemaResolverFactory.getInstance().getSchemaBindingResolver();
 resolver.mapLocationToClass("http://java.sun.com/xml/ns/j2ee/connector_1_6.xsd", JCA16MetaData.class);
 resolver.mapLocationToClass("http://java.sun.com/xml/ns/j2ee/connector_1_5.xsd", JCA15MetaData.class);
 resolver.mapLocationToClass("connector_1_5.dtd", JCA15DTDMetaData.class);
 resolver.mapLocationToClass("connector_1_6.dtd", JCA16DTDMetaData.class);
 resolver.mapLocationToClass("connector", JCA16DefaultNSMetaData.class);

using the JBXB and JBMETA classes.

[aloubyansky]

I can't tell you what's missing here from that. Enable trace for org.jboss.xb.binding.sunday.unmarshalling.XsdBinder and see what's being bound based on XSD.

[jesper.pedersen]

I have updated the TRACE log file (org.jboss.xb) on the JIRA.

Let me know if there is anything else I can supply.

[aloubyansky]

Passing connector_1_5.xsd to mapLocationToClass instead of the full URL should solve the issue.

[jesper.pedersen]

That helped a lot, thanks :)

I have attached a new profile of the startup to the issue if you think there is anything else to be gained. But most of the time is now spend in org.jboss.reflect.

If the call stack is ok I think you can resolve the issue, but some additional documentation about this would be nice.