WFS transactions should work for features with null geometry

[tschaub]

Ticket #2033 dealt with features that have no geometry field in the schema.

It is also acceptable to have a geometry field and issue transactions with null geometry.

[tschaub]

handle null geometry

[tschaub]

Tests pass. Thanks for any review.

[ahocevar]

Thanks for the verbose tests. Great work. Please commit.

[tschaub]

Thanks for the review. Closed w/ r11031.

[tschaub]

Ok, so it turns out that while GeoServer accepts <wfs:Value></wfs:Value> as a null for Geometry, the correct way to do an update with a property value of null is to omit the <wfs:Value> element altogether.

[tschaub]

omit wfs:Value element for all null values

[tschaub]

We already had the correct behavior in the <wfs:Property> writer. Where this writer encounters null values, it writes a <wfs:Name> but not a wfs:Value element. The exception with geometry was because we were waiting to set the format's srsName property until the geometry was written. By setting srsName earlier, we can pass the geometry along to the <wfs:Property> writer and this does the right thing if the geometry is null.

Tests passing. Thanks for review.

[ahocevar]

Looks like a simple fix, but I can imagine it took some quite some time to find this very elegant solution! Thanks for the hard work on this. Assuming that tests pass, please commit.

[tschaub]

Thanks for the review. Closed w/ r11034.