[Geoserver-users] WFS cascaded layers: read only exception

GeoServer GeoServer User
1

Hi,

What server supports is one thing and if feature type is editable is another. An editable layer contains “Operations” in the GetCapabilities, like this:

lv:editable_polygons

Editable test layer with polygon geometries

Editable test layer with polygon geometries

EPSG:3067

-Jukka Rahkonen-

···

Lähettäjä: Alexandre Djioev [mailto:djioev@anonymised.com]
Lähetetty: 4. joulukuuta 2013 12:42
Vastaanottaja: Andrea Aime
Kopio: Mauro Bartolomeoli; geoserver-users
Aihe: Re: [Geoserver-users] WFS cascaded layers: read only exception

Hi Amie and Mauro,

thank you, will try it. does it mean that cascading downgrades WFS to version 1.0?

Also what do you mean by securing WFS service in geoserver? Original WFS supports transactions and its open to any client.

Server is private, not mine, need permission for sharing it first. But I’ve checked capabilities document, its got transaction part:

<ows:Operation name=“Transaction”>

ows:DCP

ows:HTTP

<ows:Get xlink:href=“http://ip-addr/server/v1/wfs/?”/>

<ows:Post xlink:href=“http://ip-addr/server/v1/wfs/”/>

</ows:HTTP>

</ows:DCP>

<ows:Parameter name=“inputFormat”>

ows:Valuetext/xml; subtype=gml/2.1.2</ows:Value>

ows:Valuetext/xml; subtype=gml/3.1.1</ows:Value>

ows:Valueapplication/gml+xml; version=3.2</ows:Value>

ows:Valueapplication/json</ows:Value>

</ows:Parameter>

<ows:Parameter name=“idgen”>

ows:ValueGenerateNew</ows:Value>

ows:ValueUseExisting</ows:Value>

ows:ValueReplaceDuplicate</ows:Value>

</ows:Parameter>

<ows:Parameter name=“releaseAction”>

ows:ValueALL</ows:Value>

ows:ValueSOME</ows:Value>

</ows:Parameter>

Thanks Alex

On Wed, Dec 4, 2013 at 9:26 PM, Andrea Aime <andrea.aime@anonymised.com…> wrote:

On Wed, Dec 4, 2013 at 11:05 AM, Mauro Bartolomeoli <mauro.bartolomeoli@anonymised.com> wrote:

2013/12/4 Alexandre Djioev <djioev@anonymised.com>

Hi Mauro,

  1. Yes, server does support WFS-T.

  2. It supports WFS version 1.0, 1.1 and 2.0. As far as I understand cascading doesn’t support v2.0 so I had to include version=1.1.0 param when I pass getCapabillities string to the store config.

  3. I even tried to to cascade WFS layers from one geoserver to another and ended up with the same exception.

I tried to look at the code, and it seems read-only is forced if the capabilities document doesn’t contain “Transaction” in the Request section of the Capabilities.

This can happen if the wfs service is secured in geoserver. Is this your case?

Can you also please check (and maybe share with us) the capabilities document of your WFS-T server?

HI Mauro and Alexandre,

as far as I know the WFS datastore can cascade writes only with the 1.0.0 protocol.

Alexandre, I’d suggest you force &version=1.0.0 in the capabilities document and try again

Cheers

Andrea

–

==

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

==

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

–
Cheers, Alex