Enhanced Filter200XmlDecoder to throw an Exception if a Literal with gml-Geometry subelement is parsed #642
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
copierrj
added a commit
that referenced
this pull request
Dec 10, 2015
…anOrEqualToContainsGmlGeometry-292 Enhanced Filter200XmlDecoder to throw an Exception if a Literal with gml-Geometry subelement is parsed
lgoltz
deleted the
throwExceptionIfPropertyIsLessThanOrEqualToContainsGmlGeometry-292
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 pull requests lets the Filter200XmlDecoder throw an XMLParsingException if a Literal with gml-Geometry is detected. The handling of the WFS 2.0.0 is changed to throw an OperationProcessingFailed in case of a XMLParsingException.
The WFS 2.0.0 cite Testsuite is fixed by this pull request (Testclass org.opengis.cite.iso19142.basic.filter.ComparisonOperatorTests, Method invalidOperand_boundedBy()).