Hi, looking into the Wicket UI configuration panels a question came up. As you may know, in 1.7.x we already have an "alias" field that allow for renaming feature types before publication. That feature works only for vector layers.
On trunk we're using the new catalog objects directly and the situation is... somewhat funny. ResourceInfo has an alias field. Meaning, it can be configured for both vectors and rasters, thought only vectors have the machinery for resource renaming in place (only the type, not the attributes). In LayerInfo we have a property name, that atm is editable, and that is not necessarily the resource name, not its alias (oh my). As the icing on the cake, afaik WFS and WCS use resources directly, not layers, so the layer name is pretty much ignored, _but_, always afaik, WMS has been recoded to use layers, so WMS will see the layer name but not the resource alias. I guess we need to make up our minds and decide on _one_ way to rename stuff. I guess the best long term solution is to use the layer name? But then again, that is not namespaced. Do we namespace it? Does it make sense? Also, doing that would require to re-hook WFS and WCS to layers as opposed to resources. Not doing that would leave WMS as the "oddball" that uses the layer names instead (hmmm... how are namespaces handled there now???) Glab... Opinions? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
