Fixes namespace bindings of ValueReference when updating property in WFS-T 2.0.0 #705
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fix targets the transaction functionality of WFS 2.0.0.
Previously, when a ValueReference was updated by an update transaction the namespace was not considered. Instead, the default namespace of the FeatureType was used.
For example (POST body of update request):
In the current implementation of deegree the property app:name is updated instead of gml:name.
This fix introduces a determination of the namespace URI for properties. The so determined namespace is used to update the property then. If no namespace binding is given or it does not match any namespace URI, the previous behaviour is retained: The namespace of the FeatureType is used.