Return to Issues Table 

LockFeature Tests are issued even though the Lock attribute is not in FeatureTypeList

Issue ID#:
940
Category:
WFS/FE 1.1
Type:
Status:
Responded
Priority:
High
Entered By:
Tillman, Stan
Created On:
2014-03-18 10:03:42
Updated By:
Bermudez, Luis
Last Update:
2014-03-25 15:50:57
Assigned To:
Bermudez, Luis

Original Issue Details:

In our testing of WFS-T, we building on top of GML data and for that format we do not support FeatureLocking.  For all of our WFS services that are set up for transactions, we include Transactions and LockFeature in our Operations Metadata.  However, for some formats such as GML, we do not include the Lock attribute in the FeatureTypeList.  Because that is not set, the tests should not be sending LockFeature requests.  This is similar to a service that supports Transactions in the Operations Metadata, but only allows Add or Update capabilities through the FeatureTypeList attributes.  Here is our endpoint for reference:


http://ogc.intergraph.com/erdas-apollo/vector/WFSTCITE?Service=WFS&REQUEST=GetCapabilities


Status: Responded
Assigned To: Goerke, Sebastian

Hi Stan,


 


so the issue is, that LockFeature requests are sent anyway?


I will have a look into the CTL scripts and also into the spec to be sure such a behaviour is covered by it.


 

Hours Worked: 0.00
Entered By: Goerke, Sebastian - 2014-03-18 10:43:46
Status: Responded
Assigned To: Goerke, Sebastian

I am getting 500 Server errors when requesting your reference endpoint.

Hours Worked: 0.00
Entered By: Goerke, Sebastian - 2014-03-19 04:42:12
Status: Responded
Assigned To: Bermudez, Luis

I did an analysis of the specification and the tests related to your question.


The <Operations> elements within the FeatureTypeList are optional following the XSD schema and assertions within the specification. That said the tests are not checking for the occurence.


As there is still no abstract test suite for WFS 1.1.0 I am not sure, how to handle this issue.


I understand your requirement here Stan, but I am not sure, if it is maintenance work to add a complete setup of new tests to an existing testsuite (it is not just for the "lock" value, it should be for all possibilities then.)


Maybe Luis can give a statement? Or shall we postpone this to the WFS SWG?

Hours Worked: 0.00
Entered By: Goerke, Sebastian - 2014-03-19 05:14:45
Status: Responded
Assigned To: Bermudez, Luis

I agree with Sebastian last point.  Although I only mentioned the "lock" value, it should be applied for all of the possible values. 


And I agree it is optional because that is how you tag which FeatureTypes support the possible values (add, delete, update, lock).  I have just mentioned it to Luis and we are going to speak about it later.

Hours Worked: 0.00
Entered By: Tillman, Stan - 2014-03-24 10:41:51
Status: Responded
Assigned To: Bermudez, Luis

I found in the description of the test that the locking is optional.


http://cite.opengeospatial.org/teamengine/about/wfs/1.1.0/web/


 


We should check to see if the "lock" is advertized at the feature type to do the lock test.


This doesn't apply to the other operations.


 

Hours Worked: 0.00
Entered By: Bermudez, Luis - 2014-03-25 15:50:57