rini.angre...@csiro.au ha scritto: > Hello app-schema enthusiasts, > > I have a question regarding layer.xml. Feature chaining lets us break up > mappings for different types, including non-feature types, eg. data > type (so they can be reusable, ie. if a non-feature type A is nested > inside type B and C, I only need to create the config once). The problem > is these non-feature types also appear inside feature type list in > GetCapabilities output. > I spoke to Gabriel during his visit in Perth, and he said that if the > layer is disabled, the type shouldn't appear in GetCapabilities. > This makes sense to me, since enabled layers would let us run > getFeatures on the type via the UI. So if we can't see the features (ie. > the layer is disabled), why should it show in GetCapabilities. > The problem is, regardless of whether or not the layer.xml is disabled, > or non-existent, all types would still appear in GetCapabilities. > Is this a bug? Can someone tell me the true purpose of this layer setting..
The resource/publishing split is not done, this means the current catalog behaves a lot like the old one. WFS and WCS services are still coded against the resources, the layer is almost ignored, so I guess you'll have to disable the resources in order to avoid having them show up in the capabilities. Now, when you do that, I'm not sure you'll still be able to grab feature sources out of them thought (did not check) Cheers Andrea -- Andrea Aime 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
