unknownFeatureIdentifier test should expect exception about ets-wfs20 HOT 4 CLOSED

A possible fix is to remove the (optional) TYPENAMES parameter from the request. Another test (inconsistentFeatureIdentifierAndType) should then be added to check for the exceptional condition.

from ets-wfs20.

Removed the typeNames parameter from the unknownFeatureIdentifier test, since it is not required when ResourceId is given. Added new test inconsistentFeatureIdentifierAndType to elicit an exception report when these parameters are both present but are not consistent.

from ets-wfs20.

From cl. 7.9.2.4.1 in the WFS 2.0 specification:

The TYPENAMES parameter is mandatory in all cases except when the RESOURCEID parameter is specified. In this case the TYPENAMES parameter may be omitted because each feature instance can be identified by its resource identifier alone (see 7.2).

from ets-wfs20.

Reintroduce the typeNames param, since it is required in XML request entities. This is an inconsistency in the spec which should be the subject of a CR.

Also, this statement appears to apply only to identifiers for which features instances exist (italics added): "If both the TYPENAMES and RESOURCEID parameters are specified then all the feature instances identified by the RESOURCEID parameter shall be of the type specified by the TYPENAMES parameter;"

Therefore an exception report should not be produced in this case--just a normal response with no feature members.

from ets-wfs20.