From: <ad...@jb...> - 2005-10-31 17:30:34
|
| 1 DEBUG [JbxbPojoServerUnitTestCase] ==== Starting testSimpleCollection ==== | 1 DEBUG [JbxbPojoServerUnitTestCase] ================ Getting Schema Binding | 66 TRACE [Util] loading xsd: /home/adrian/jboss-head/workspace/testsuite/src/resources/xml/jbxb-bean-deployer_1_0.xsd | 700 TRACE [Util] Loaded xsd: /home/adrian/jboss-head/workspace/testsuite/src/resources/xml/jbxb-bean-deployer_1_0.xsd in 634ms | ... | 2398 DEBUG [JbxbPojoServerUnitTestCase] ================ Got Schema Binding in 2397ms | ... | 3036 DEBUG [JbxbPojoServerUnitTestCase] testSimpleCollection took 3035ms | The schema/annotation parsing seems to be taking a long time, admittedly I have TRACE logging enabled. Without TRACE logging: | 0 DEBUG [JbxbPojoServerUnitTestCase] ==== Starting testSimpleCollection ==== | 0 DEBUG [JbxbPojoServerUnitTestCase] ================ Getting Schema Binding | 1607 DEBUG [JbxbPojoServerUnitTestCase] ================ Got Schema Binding in 1606ms | ... | 2189 DEBUG [JbxbPojoServerUnitTestCase] testSimpleCollection took 2189ms | 2189 DEBUG [JbxbPojoServerUnitTestCase] ==== Stopping testSimpleCollection ==== | The problem appears to be that it does a first pass of the parsing using Xerces to load the model | Util.loadSchema | XSModel model = schemaLoader.loadURI(xsdURL); | then it parses each annotation individually using a new parser for each. Are there any plans to improve this? Wouldn't it be better to just write our own XSD model/parser and remove the dependency on Xerces altogether? i.e. any SAX parser could be used. The only related issue I can find is a (bad in my opinion) request from the WS team to get a hold of the Xerces model from JBossXB. http://jira.jboss.com/jira/browse/JBXB-33 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3904462#3904462 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3904462 |