Re: [Geoserver-users] Null namespace in WFS response for layer based on disabled PostGIS store [SEC=UNCLASSIFIED]

[Ben Caradoc-Davies]

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 Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Null namespace in WFS response for layer based on disabled PostGIS store [SEC=UNCLASSIFIED]

[Johnson, Steven (Contractor)]

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 the store is available but disabled in GeoServer.

From: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
Sent: Wednesday, 12 October, 2016 5:13 a.m.
To: Ben Caradoc-Davies
Cc: Johnson, Steven (Contractor); geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Null namespace in WFS response for layer based 
on disabled PostGIS store [SEC=UNCLASSIFIED]

On Tue, Oct 11, 2016 at 8:19 PM, Ben Caradoc-Davies 
> wrote:
Andrea, I am sure you are right. I have closed this one as duplicated by 
GEOS-7792 (which links to this thread and the fixes for disabled layers). I 
note that I did not see the null behaviour in my tests with WFS 2.0 / GML 3.2.

Interesting, I've tried a similar path to the one that triggers the wfs 1.1 
null prefixes, but using the wfs 2.0 protocol, and I indeed could not reproduce 
either... not sure why?
This is what I've tried, on a freshly start up GeoServer:
http://localhost:8080/geoserver/topp/ows?service=WFS=2.0.0=GetFeature=topp:tasmania_cities=1
http://localhost:8080/geoserver/sf/ows?service=WFS=2.0.0=GetFeature=sf:roads=1

Cheers
Andrea

--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it


AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i 
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo 
è consentito esclusivamente al destinatario del messaggio, per le finalità 
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne 
il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di 
procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro 
sistema. Conservare il messaggio stesso, divulgarlo anche in parte, 
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, 
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for the 
attention and use of the named addressee(s) and may be confidential or 
proprietary in nature or covered by the provisions of privacy act (Legislative 
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in 
accord with its purpose, any disclosure, reproduction, copying, distribution, 
or either dissemination, either whole or partial, is strictly forbidden except 
previous formal approval of the named addressee(s). If you are not the intended 
recipient, please contact immediately the sender by telephone, fax or e-mail 
and delete the information in this message that has been received in error. The 
sender does not give any warranty or accept liability as the content, accuracy 
or completeness of sent messages and accepts no responsibility  for changes 
made after they were sent or for other risks which arise as a result of e-mail 
transmission, viruses, etc.

---

IMPORTANT: This email remains the property of the Department of Defence and is 
subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have 
received this email in error, you are requested to contact the sender and 
delete the email.
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Null namespace in WFS response for layer based on disabled PostGIS store [SEC=UNCLASSIFIED]

[Ben Caradoc-Davies]

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 even after the store is disabled. This is a bug.
> Actually both known issues:
> https://osgeo-org.atlassian.net/browse/GEOS-6980

Andrea, I am sure you are right. I have closed this one as duplicated by 
GEOS-7792 (which links to this thread and the fixes for disabled 
layers). I note that I did not see the null behaviour in my tests with 
WFS 2.0 / GML 3.2.

Kind regards,

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Null namespace in WFS response for layer based on disabled PostGIS store [SEC=UNCLASSIFIED]

[Andrea Aime]

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 disabled. This is a bug.
>

Actually both known issues:
https://osgeo-org.atlassian.net/browse/GEOS-6980
https://osgeo-org.atlassian.net/browse/GEOS-4773

The first one should does not look to be too hard to fix, the second one
looks hard
instead.

Cheers
Andrea

-- 
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

---
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Null namespace in WFS response for layer based on disabled PostGIS store [SEC=UNCLASSIFIED]

[Ben Caradoc-Davies]

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: 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 confirm that PostGIS feature types continue to be served via WFS
>> service URLs even after the store is disabled. This is a bug.
>

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Null namespace in WFS response for layer based on disabled PostGIS store [SEC=UNCLASSIFIED]

[Ben Caradoc-Davies]

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 confirm that PostGIS feature types continue to be served via WFS
> service URLs even after the store is disabled. This is a bug.

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Null namespace in WFS response for layer based on disabled PostGIS store [SEC=UNCLASSIFIED]

[Ben Caradoc-Davies]

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 disabled 
data store.

A disabled data store can be re-enabled using the REST API. If you 
monitor your WFS service with (for example) nagios, you can re-enable 
the data store with a REST operation when the service is down. For 
example, I made a test:bugsites PostGIS store, disabled it in the web 
UI, then re-enabled it with:

curl -v -u admin:geoserver -XGET 
'http://localhost:8080/geoserver/rest/workspaces/test/datastores/bugsites.xml' 
 > bugsites.xml

perl -pi -e 's|false|true|' 
bugsites.xml

curl -v -u admin:geoserver -XPUT -d @bugsites.xml -H 'Content-Type: 
text/xml' 
'http://localhost:8080/geoserver/rest/workspaces/test/datastores/bugsites.xml'

Immediately after this call, the previously published feature type was 
available in layer previews.

There are many REST API examples in the manual:
http://docs.geoserver.org/stable/en/user/rest/examples/curl.html

Kind regards,
Ben.

On 11/10/16 14:00, Johnson, Steven (Contractor) wrote:
> 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 
> previously down but then becomes available?
>
>
> IMPORTANT: This email remains the property of the Department of Defence and 
> is subject to the jurisdiction of section 70 of the Crimes Act 1914. If you 
> have received this email in error, you are requested to contact the sender 
> and delete the email.
> From: Johnson, Steven (Contractor) [mailto:steven.john...@dsto.defence.gov.au]
> Sent: Friday, 26 August, 2016 9:49 a.m.
> To: geoserver-users@lists.sourceforge.net
> Subject: [Geoserver-users] Null namespace in WFS response for layer based on 
> disabled PostGIS store [SEC=UNCLASSIFIED]
>
>
> 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 have a couple of questions 
> regarding this, with further details to follow.
>
> 1.   Should I be able to make a WFS request to a layer that uses a 
> disabled store and get valid features assuming the underlying store (i.e. 
> PostGIS/PostgreSQL) is actually available?
>
> 2.   If (1) is true (i.e. I can make a WFS request and get a response 
> with appropriate features when the store is disabled) why is the namespace 
> null for the feature member elements and missing for the feature properties? 
> Is this a bug, due to something I have configured incorrectly, or expected 
> behaviour?
>
> The situation is I have a PostGIS datastore running on a separate host from 
> GeoServer, and if the PostGIS store is disabled in GeoServer but actually up 
> and available I can make a WFS GetFeature request and get a response with 
> valid features except that there is a null namespace in the response for each 
> feature member element and the feature properties. This situation came about 
> because we had restarted both the GeoServer and PostGIS hosts and GeoServer 
> had restarted before PostGIS and hence marked the store as disabled. However 
> I can recreate the same symptoms simply by disabling the PostGIS store and 
> then sending the WFS request for the layer. Re-enabling the PostGIS store and 
> sending the WFS request again then results in the "correct" response with the 
> expected namespace. We initially didn't notice the disabled PostGIS store but 
> could still make WFS requests and get features back except that our client 
> was expecting the "normal" namespace (i.e. agiist) and not the "null" namespa
 ce and hence complained.
>
> A snippet of the WFS response with the null namespace (i.e. made while the 
> PostGIS store is disabled) is as follows:
>
> 
> http://www.w3.org/2001/XMLSchema; 
> xmlns:serval="http://xyz; xmlns:wfs="http://www.opengis.net/wfs; 
> xmlns:gml="http://www.opengis.net/gml; xmlns:ogc="http://www.opengis.net/ogc; 
> xmlns:ows="http://www.opengis.net/ows; 
> xmlns:xlink="http://www.w3.org/1999/xlink; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; numberOfFeatures="40" 
> timeStamp="2016-08-25T23:40:35.720Z" 
> xsi:schemaLocation="http://www.opengis.net/wfs 
> http://xyzhost:80/geoserver/schemas/wfs/1.1.0/wfs.xsd http://xyz/agiist 
> 

Re: [Geoserver-users] Null namespace in WFS response for layer based on disabled PostGIS store [SEC=UNCLASSIFIED]

[Johnson, Steven (Contractor)]

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 
previously down but then becomes available?


IMPORTANT: This email remains the property of the Department of Defence and is 
subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have 
received this email in error, you are requested to contact the sender and 
delete the email.
From: Johnson, Steven (Contractor) [mailto:steven.john...@dsto.defence.gov.au]
Sent: Friday, 26 August, 2016 9:49 a.m.
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] Null namespace in WFS response for layer based on 
disabled PostGIS store [SEC=UNCLASSIFIED]


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 have a couple of questions regarding 
this, with further details to follow.

1.   Should I be able to make a WFS request to a layer that uses a disabled 
store and get valid features assuming the underlying store (i.e. 
PostGIS/PostgreSQL) is actually available?

2.   If (1) is true (i.e. I can make a WFS request and get a response with 
appropriate features when the store is disabled) why is the namespace null for 
the feature member elements and missing for the feature properties? Is this a 
bug, due to something I have configured incorrectly, or expected behaviour?

The situation is I have a PostGIS datastore running on a separate host from 
GeoServer, and if the PostGIS store is disabled in GeoServer but actually up 
and available I can make a WFS GetFeature request and get a response with valid 
features except that there is a null namespace in the response for each feature 
member element and the feature properties. This situation came about because we 
had restarted both the GeoServer and PostGIS hosts and GeoServer had restarted 
before PostGIS and hence marked the store as disabled. However I can recreate 
the same symptoms simply by disabling the PostGIS store and then sending the 
WFS request for the layer. Re-enabling the PostGIS store and sending the WFS 
request again then results in the "correct" response with the expected 
namespace. We initially didn't notice the disabled PostGIS store but could 
still make WFS requests and get features back except that our client was 
expecting the "normal" namespace (i.e. agiist) and not the "null" namespace and 
hence complained.

A snippet of the WFS response with the null namespace (i.e. made while the 
PostGIS store is disabled) is as follows:


http://www.w3.org/2001/XMLSchema; 
xmlns:serval="http://xyz; xmlns:wfs="http://www.opengis.net/wfs; 
xmlns:gml="http://www.opengis.net/gml; xmlns:ogc="http://www.opengis.net/ogc; 
xmlns:ows="http://www.opengis.net/ows; 
xmlns:xlink="http://www.w3.org/1999/xlink; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; numberOfFeatures="40" 
timeStamp="2016-08-25T23:40:35.720Z" 
xsi:schemaLocation="http://www.opengis.net/wfs 
http://xyzhost:80/geoserver/schemas/wfs/1.1.0/wfs.xsd http://xyz/agiist 
http://xyzhost:80/geoserver/wfs?service=WFSversion=1.1.0request=DescribeFeatureTypetypeName=agiist%3Agazetteer_geonames">

...


http://xyz/agiist; 
gml:id="gazetteer_geonames.fid--405349f1_156b66476cd_-6384">
Blaha (historical)

...

http://xyz/agiist;>Blaha (historical)
http://xyz/agiist;>43.08333
http://xyz/agiist;>-97.78333
http://xyz/agiist;>US
...
 
...




A snippet of the "correct" WFS response (i.e. made while the PostGIS store is 
enabled) is as follows:


http://www.w3.org/2001/XMLSchema; 
xmlns:serval="http://xyz; xmlns:wfs="http://www.opengis.net/wfs; 
xmlns:agiist="http://xyz/agiist; xmlns:gml="http://www.opengis.net/gml; 
xmlns:ogc="http://www.opengis.net/ogc; xmlns:ows="http://www.opengis.net/ows; 
xmlns:xlink="http://www.w3.org/1999/xlink; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; numberOfFeatures="40" 
timeStamp="2016-08-25T07:15:06.500Z" 
xsi:schemaLocation="http://www.opengis.net/wfs 
http://xyzhost:80/geoserver/schemas/wfs/1.1.0/wfs.xsd http://xyz/agiist 

[Geoserver-users] Null namespace in WFS response for layer based on disabled PostGIS store [SEC=UNCLASSIFIED]

[Johnson, Steven (Contractor)]

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 have a couple of questions regarding 
this, with further details to follow.

1.   Should I be able to make a WFS request to a layer that uses a disabled 
store and get valid features assuming the underlying store (i.e. 
PostGIS/PostgreSQL) is actually available?

2.   If (1) is true (i.e. I can make a WFS request and get a response with 
appropriate features when the store is disabled) why is the namespace null for 
the feature member elements and missing for the feature properties? Is this a 
bug, due to something I have configured incorrectly, or expected behaviour?

The situation is I have a PostGIS datastore running on a separate host from 
GeoServer, and if the PostGIS store is disabled in GeoServer but actually up 
and available I can make a WFS GetFeature request and get a response with valid 
features except that there is a null namespace in the response for each feature 
member element and the feature properties. This situation came about because we 
had restarted both the GeoServer and PostGIS hosts and GeoServer had restarted 
before PostGIS and hence marked the store as disabled. However I can recreate 
the same symptoms simply by disabling the PostGIS store and then sending the 
WFS request for the layer. Re-enabling the PostGIS store and sending the WFS 
request again then results in the "correct" response with the expected 
namespace. We initially didn't notice the disabled PostGIS store but could 
still make WFS requests and get features back except that our client was 
expecting the "normal" namespace (i.e. agiist) and not the "null" namespace and 
hence complained.

A snippet of the WFS response with the null namespace (i.e. made while the 
PostGIS store is disabled) is as follows:


http://www.w3.org/2001/XMLSchema; 
xmlns:serval="http://xyz; xmlns:wfs="http://www.opengis.net/wfs; 
xmlns:gml="http://www.opengis.net/gml; xmlns:ogc="http://www.opengis.net/ogc; 
xmlns:ows="http://www.opengis.net/ows; 
xmlns:xlink="http://www.w3.org/1999/xlink; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; numberOfFeatures="40" 
timeStamp="2016-08-25T23:40:35.720Z" 
xsi:schemaLocation="http://www.opengis.net/wfs 
http://xyzhost:80/geoserver/schemas/wfs/1.1.0/wfs.xsd http://xyz/agiist 
http://xyzhost:80/geoserver/wfs?service=WFSversion=1.1.0request=DescribeFeatureTypetypeName=agiist%3Agazetteer_geonames;>

...


http://xyz/agiist; 
gml:id="gazetteer_geonames.fid--405349f1_156b66476cd_-6384">
Blaha (historical)

...

http://xyz/agiist;>Blaha (historical)
http://xyz/agiist;>43.08333
http://xyz/agiist;>-97.78333
http://xyz/agiist;>US
...
 
...




A snippet of the "correct" WFS response (i.e. made while the PostGIS store is 
enabled) is as follows:


http://www.w3.org/2001/XMLSchema; 
xmlns:serval="http://xyz; xmlns:wfs="http://www.opengis.net/wfs; 
xmlns:agiist="http://xyz/agiist; xmlns:gml="http://www.opengis.net/gml; 
xmlns:ogc="http://www.opengis.net/ogc; xmlns:ows="http://www.opengis.net/ows; 
xmlns:xlink="http://www.w3.org/1999/xlink; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; numberOfFeatures="40" 
timeStamp="2016-08-25T07:15:06.500Z" 
xsi:schemaLocation="http://www.opengis.net/wfs 
http://xyzhost:80/geoserver/schemas/wfs/1.1.0/wfs.xsd http://xyz/agiist 
http://xyzhost:80/geoserver/wfs?service=WFSversion=1.1.0request=DescribeFeatureTypetypeName=agiist%3Agazetteer_geonames;>

...



Blaha (historical)

...

Blaha (historical)
43.08333
-97.78333
US
...

...



Finally, if all of this is expected behaviour then can GeoServer automatically 
re-enable a store if it becomes available or is it simply up to a GeoServer 
administrator to manually go in and re-enable it? It would be nice for 
GeoServer to be tolerant of a PostGIS store potentially being unavailable or 
dropping out and then becoming available/online.

Regards,
Steve Johnson

IMPORTANT: This email remains the property of the Department of Defence and is 
subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have 
received this email in error, you are requested to contact the sender and 
delete the email.
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users