Hi,
Can you include the full XML document you are sending for the request. Also
can you replicate the problem against any layer, say one of the layers that
ships with GeoServer?
Thanks.
-Justin
On Tue, Nov 2, 2010 at 4:00 PM, phony baloney phonybalone...@gmail.comwrote:
Hi all,
First time
On Wed, Nov 3, 2010 at 3:17 PM, Justin Deoliveira jdeol...@opengeo.org wrote:
Hi,
Can you include the full XML document you are sending for the request. Also
can you replicate the problem against any layer, say one of the layers that
ships with GeoServer?
Wondering... might it be due to
Hey guys,
Thanks for the swift responses.
I took your advice and tried to reproduce the results. In the process of
doing that, I came to realize that this was in fact user error.
Basically a colleague of mine had been working on a WFS client and had been
constructing the original XML requests
Hi all,
First time writer/subscriber to the list.
I've been experimenting with POST'd XML WFS requests in GeoServer 2.02
recently and have observed some strange results. Basically, according to my
understanding of the OGC WFS and filter specifications, in a valid WFS
request sent via XML, every
