[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[udig-devel] [jira] Created: (UDIG-1673) Generated WFS-T requests seriously broken (e.g. invalid filter)
|
Generated WFS-T requests seriously broken (e.g. invalid filter)
---------------------------------------------------------------
Key: UDIG-1673
URL: http://jira.codehaus.org/browse/UDIG-1673
Project: uDIG
Issue Type: Bug
Components: webservices
Affects Versions: UDIG 1.2.RC3
Reporter: H. Rubach
When working with WFS-T, the generated requests are invalid and cannot be processed by service implementations that rely on correct requests (tested with deegree 3 WFS).
The attached files have been generated by uDig (just augmented with xsi:schemaLocation attributes, so you can easily check that they don't validate, e.g. in XMLSpy or Eclipse).
The requests udig-delete.xml and udig-update.xml have been produced for deleting and updating. They contain the following errors:
- lockAction attribute not allowed for WFS 1.0.0 requests (invalid, but no problem with deegree WFS)
- Filter contains nested Filter element (severe problem, Filter cannot be parsed)
For inserting, uDig didn't get to issuing the insert transaction, because it initiates the process by sending some GetFeature requests that are already broken which causes service exceptions. Errors in the GetFeature requests (udig-getfeature*.xml):
- Filters use bogus feature id unknown to the service, "newhk:GGD.9223372036854775807", newhw-prefix seems to be made up by uDig (?)
- Filter contains nested Filter element (severe problem, Filter cannot be parsed)
- Additionally (in udig-getfeature3.xml), a filter is used that always evaluates to false
For enabling the possibility to use uDig with other WFS implementation than GeoServer, it would be much appreciated if these issues could be fixed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
