WFS 2.0 Constrains not in sync with Service Level

Description

Steps to reproduce:

1. Change Service Level to <b>Basic</b>
2. Review GetCapabilities

 

I expect the constrains should be FALSE if the service is not currently providing ImplementsTransactionWFS and ImplementsLockingWFS.

Environment

None

Activity

Show:
codehaus
April 10, 2015, 4:41 PM

CodeHaus Comment From: jgarnett - Time: Tue, 3 Mar 2015 18:36:06 -0600
---------------------
<p>So a really old regression then <img class="emoticon" src="https://jira.codehaus.org/images/icons/emoticons/smile.gif" height="16" width="16" align="absmiddle" alt="" border="0"/> grumble grumble ... </p>

codehaus
April 10, 2015, 4:41 PM

CodeHaus Comment From: aaime - Time: Wed, 4 Mar 2015 01:40:55 -0600
---------------------
<p>Confused... we do support Transaction in WFS 2.0, don't we?</p>

codehaus
April 10, 2015, 4:41 PM

CodeHaus Comment From: jratike80 - Time: Wed, 4 Mar 2015 01:54:14 -0600
---------------------
<p>Start reading from the top:

Steps to reproduce:

1. Change Service Level to <b>Basic</b></p>

<p>Issue is that denying transactions do remove transactions from advertised operations but it does not change the value of ImplementsTransactionalWFS constraint.</p>

<p>I would not be surprised if that has never worked with any GS version because it is new to WFS 2.0 and it is only metadata. Perhaps nobody has ever tested it.</p>

Jukka Rahkonen
July 25, 2016, 10:47 PM

Situation is the same with Geoserver 2.0. When WFS is set to BASIC level the GetCapabilities still announce:

Jody Garnett
August 15, 2018, 5:44 PM

Question: Does the transaction operation still function?

It is one thing if the transaction operation is listed incorrectly, but more serious if the operation was intended to be disabled and is still usable by clients.

Assignee

Unassigned

Reporter

codehaus

Triage

None

Fix versions

None

Affects versions

Components

Priority

Medium
Configure