Hi Andrea, Yes, I agree that the situation now is not ideal. Currently ResourceInfo has:
getName() -> its published name (what we call alias today) getNativeName() -> the physical name getAlias() -> collection of "aliases" I believe we achieve aliasing now with getName() and getNativeName(). I agree that Layer.getName() is the best long term solution for a published name. But as you point out this requires that we have services go through Layers, not resources -> ie, the resource/publishing split we oh so long for. Part of that is introducing maps so that layer names can be qualified. So the map will become the "namespace" for the layer name. Or at least that is how i see it playing out. Andrea Aime wrote: > 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 > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ 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
