Configuration reader triggers bounds computation for that whose native bbox is not known
----------------------------------------------------------------------------------------
Key: GEOS-2588
URL: http://jira.codehaus.org/browse/GEOS-2588
Project: GeoServer
Issue Type: Improvement
Components: Global
Affects Versions: 1.7.2
Reporter: Andrea Aime
Assignee: Andrea Aime
Priority: Critical
Fix For: 1.7.3
LegacyCatalogImporter at line 486 assumes it has to compute the native bbox if it is not available in the configuration.
This basically locks up GeoServer startup when the user did not use the "generate" button to compute the bounds in the UI, usually because computing the bounds would have taken minutes, hours or days (classic case of very huge data sets stored in the db).
If the native bounds are not there, they should not be computed. Either that, or we try to generate them by back-projecting the geographic ones, but never, ever, compute them manually, the operation is very cheap on shapefiles, but may be a killer on spatial dbms
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira