Bug report #6552

WFS client: Filter Element contains incoherent XML Namespaces

Added by aperi2007 - over 7 years ago. Updated over 4 years ago.

Status:Closed
Priority:Normal
Assignee:-
Category:Web Services clients/WFS
Affected QGIS version:master Regression?:No
Operating System: Easy fix?:No
Pull Request or Patch supplied:No Resolution:fixed/implemented
Crashes QGIS or corrupts data:No Copied to github as #:15756

Description

Hi,
In the wfs client,
the filter produced using the expression builder is not valid for a ServerWFS with validation ON.

Infact it produce a fragment like this:

<Filter><PropertyIsEqualTo><PropertyName>comune</PropertyName><Literal>FIRENZE</Literal></PropertyIsEqualTo></Filter>

sending this to a server wfs with validation on will return this exception:
Filter Element contains incoherent XML Namespaces

The right filter fragment should be this:

<Filter xmlns:wfs="http://www.opengis.net/wfs"><PropertyIsEqualTo><PropertyName>comune</PropertyName><Literal>FIRENZE</Literal></PropertyIsEqualTo></Filter>

so is missing the attribute:
xmlns:wfs="http://www.opengis.net/wfs"

Regards,


Related issues

Related to QGIS Application - Bug report #13065: WFS 1.0.0 Client requests with a GML component fail again... Closed 2015-07-02

History

#1 Updated by aperi2007 - over 7 years ago

Hi,

I discovered onlynow that the qgis wfs client is a 1.0.0 client.
(see ticket #6551).

So perhaps the validation of a WFS server 1.0 don't need the attribute
xmlns:wfs="http://www.opengis.net/wfs" ?

I don't know, my server wfs is 1.1.0 only and so I cannot test this.

Please, who know this can close eventually this ticket ?

#2 Updated by Médéric RIBREUX over 4 years ago

  • Resolution set to fixed/implemented
  • % Done changed from 0 to 100
  • Status changed from Open to Closed

Hello, bug triage...

this is fixed in QGIS 2.13 master (and probably in previous versions). Now, the filter request uses the good namespace (http://www.opengis.net/ogc).
QGIS still have a problem with WFS filters but is covered in another bug. So I am closing this one !

Also available in: Atom PDF