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..
Cheers Rini
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
