Andrea Aime wrote: > Justin Deoliveira ha scritto: >>> I saw no discussion. Looking at the diff it would seem this change >>> fixes a regression introduced during the NY sprint? (using >>> layer and their names instead of resources and their qualified names?) >> Right, I guess a chance to chime in would have been nice. Especially >> since a better fix might just be to have LayerInfoImpl.getName() call >> through to ResourceInfo.getPrefixedName() since we don't really allow >> the two to differ, and this probably will probably come up again in >> other places. > > Yup, agreed it's a better way and one we discussed and agreed upon > already. Soo... let's do it? Agreed. Note it also forces layer name to be read only for the time being and to make the UI layer name validation check weaker (for instance, ArcSDE type names have been non wfs conformant since 2003, they contain periods, something that can be fixed as per the resource/publish split when all the services use layer name, but right now it simply means we couldn't add any ArcSDE feature type).
Gabriel PS: whether to make ArcSDE type names WFS friendly as default may be a separate discussion. GeoServer may also choose to escape names somehow which in the end seems cleverer to me, as there's no real mandate on geotools type names to be GML valid? > > Cheers > Andrea > > ------------------------------------------------------------------------------ > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel -- Gabriel Roldan OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel