Steven,
this bug has been fixed on master, 2.10.x, and 2.9.x. The fix will be
included in 2.10.0, 2.9.3, and future nightly builds:
[GEOS-7792] WFS ignores disabling of stores
https://osgeo-org.atlassian.net/browse/GEOS-7792
Thank you for your detailed report.
Kind regards,
--
Ben
UNCLASSIFIED
Thanks for your help Ben and Andrea.
I guess the null namespace issue is a bit of a moot point anyway given that the
WFS should not be serving features when the store is disabled.
We'll take your advice Ben about monitoring and re-enable the datastore via the
REST API if indeed
On 11/10/16 20:39, Andrea Aime wrote:
> On Tue, Oct 11, 2016 at 4:50 AM, Ben Caradoc-Davies
> wrote:
>> I cannot reproduce on master the null namespace prefix behaviour that
>> you report.
>> I can confirm that PostGIS feature types continue to be served via WFS
>> service URLs
On Tue, Oct 11, 2016 at 4:50 AM, Ben Caradoc-Davies
wrote:
> Steven,
>
> I cannot reproduce on master the null namespace prefix behaviour that
> you report.
>
> I can confirm that PostGIS feature types continue to be served via WFS
> service URLs even after the store is
This affects shapefiles as well, and I am guessing all stores.
I have reported this as a bug:
https://osgeo-org.atlassian.net/browse/GEOS-7792
On 11/10/16 15:59, Ben Caradoc-Davies wrote:
> WMS service requests for a feature type from a disabled store fail with:
> java.io.IOException:
WMS service requests for a feature type from a disabled store fail with:
java.io.IOException: featureType: test:bugsites does not have a properly
configured datastore at
org.geoserver.wms.MapLayerInfo.getFeatureSource(MapLayerInfo.java:311)
On 11/10/16 15:50, Ben Caradoc-Davies wrote:
> I can
Steven,
I cannot reproduce on master the null namespace prefix behaviour that
you report.
I can confirm that PostGIS feature types continue to be served via WFS
service URLs even after the store is disabled. This is a bug.
As far as I know, GeoServer will not automatically re-enable a
UNCLASSIFIED
Can anyone help with this?
Is the null namespace I am seeing in WFS responses expected if a PostGIS store
is disabled in GeoServer but the actual PostGIS DB itself (on a separate host)
is available?
Is GeoServer able to automatically re-enable a PostGIS datastore that was
UNCLASSIFIED
Hi,
I am using GeoServer v2.9.1 running on Java 1.8.0_74 64 bit, Tomcat 7, Centos 7
and I am seeing a null namespace in WFS GetFeature responses when querying a
layer that uses a disabled PostGIS datastore (i.e. the underlying PostGIS is
available but is disabled in GeoServer). I