Hi, I'm trying to use CatalogBuilder.buildFeatureType() and I'm having some troubles with its behaviour, so I'm looking for ways to fix it. (see full source code here: http://svn.codehaus.org/geoserver/trunk/src/main/src/main/java/org/geoserver/catalog/CatalogBuilder.java)
The basic issue I'm having is with the method specification. That is, is the method required to build a fully usable FeatureTypeInfo, and thus throw exceptions in the case it's not possible to do so, or try a best effort to provide something ready that the user can customized later, so the focus is to fill as much fields as possible automatically? Both use cases are legitimate. The REST configuration may need the first, the Wicket UI the latter. The current implementation is a bit of both, but neither fully. For example, buildFeatureType() may set a null SRS in case the lookup fails, meaning the layer won't be usable in a valid capabilities response. Yet, if the transformation from native to lat/lon fails, an exception will be thrown back. But, if the native CRS was missing, then the lat/long bbox will be simply skipped and the feature type info returned. I think the method should be modified to just fill as much as possible without throwing exceptions, and leave the checks to whether a feature type is usable to the catalog validation routines instead, or to the UI validation, in case the feature type built like this is used to fill a new layer configuration page. Oh, UI wise we don't want to have the native bbox computed before hand as that may take various minutes when the data sets are huge (this is one of the things we had to fix for TIKE in 1.7.x). Should we add a param in that direction, or just have the bbox filling be a separate method (initBboxes(FEatureTypeInfo)? Opinions? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
