[Geoserver-devel] GeoServer does not accept its own WFS output

Hi All,

I’ve been working on a WFS implementation outside of GeoServer and was using GeoServer’s output as the gold standard for what would work, but running into a GML2 parser NullPointerException (full message on the users list: http://is.gd/aKDFl ). But today I tried hooking up my local GeoServer to the GeoServer on geoserver.org, and found that server to be misconfigured with the wrong location for layers (localhost:8080, apparently), so that breaks as well. All in all, I’m mystified how people can develop new WFS services, because GeoServer gives very little debugging information and there’s no validator I can find. I’m rather knee-deep in code right now, so any information related to this would be incredibly useful.

Thanks,

Tom MacWright

Tom MacWright ha scritto:

Hi All,

I've been working on a WFS implementation outside of GeoServer and was using GeoServer's output as the gold standard for what would work, but running into a GML2 parser NullPointerException (full message on the users list: http://is.gd/aKDFl ).

I don't really know why that is happening, could not see anything
wrong in the request. That's why I did not answer.

But today I tried hooking up my local GeoServer to the GeoServer on geoserver.org <http://geoserver.org>,

There is no GeoServer running at geoserver.org. What server are you
talking about? Full URL?

Also, what do you mean by "hooking up"? You're trying to WFS-cascade
another GeoServer? The WFS client embedded in GeoServer has unfortunately fell unmaintained, I would not be surprised if it's acting
up, none of the developers is really using it.

That said, I've just hooked up my local GeoServer to this URL:
http://demo.opengeo.org/geoserver/ows?service=wfs&version=1.0.0&request=GetCapabilities

and it works fine (tried with the states layer). Well, sort of, that server is so heavily loaded and on such a small hardware that sometimes
the request times out.

If I connect to:
http://demo.opengeo.org/geoserver/ows?service=wfs&version=1.1.0&request=GetCapabilities

instead I get some funny results... the embedded client does not account
for the axis flipping and we get a flipped map as a result...
Opened a Jira about this http://jira.codehaus.org/browse/GEOS-3860

and found that server to be misconfigured with the wrong location for layers (localhost:8080, apparently), so that breaks as well. All in all, I'm mystified how people can develop new WFS services, because GeoServer gives very little debugging information and there's no validator I can find. I'm rather knee-deep in code right now, so any information related to this would be incredibly useful.

You can enable strict validation by adding &strict=true to the URL
you're posting to. However that won't work for Insert in WFS-T.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

(attachments)

states.png