Hi, I've been looking a little on the gt2-xml-gml3 build time slowness (one of the longest to build, around 50 seconds on my PC).
The slowest among its tests is GML3EncodingTest, taking alone more than 11 seconds. Now, the funny thing is, it's not CPU bound. Little investigation shows the test takes only 3 seconds if the net is disconnected, and sysouts the following: src-resolve: Cannot resolve the name 'gml:AbstractFeatureType' to a(n) 'type definition' component. Whilst if I run it connected, surprise, no message, and it takes a lot longer -> the test is downloading something from the net, but passes also if it cannot download that stuff. I bet these are XSD files? Is there any way to avoid this, I do believe we have the necessary xsd files in the classpath too, no? Looking at other test profiles, it seems each one of them is using 90% of its time loading and parsing schema files (SchemaLocator.locateSchema() calls). Wondering, since the parser is schema driven, and thus we need to load it, can't we stick the loaded schema into an in memory cache so that we pay the loading price just once? I'm not talking of a perennial cache, a LRU one should be ok, or something time based, that purges stuff if it's not used for some seconds/minutes Cheers Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
