fix WMS getMap unhandled exception#12372
Open
stefanocudini wants to merge 2 commits into
Open
Conversation
added test remove xml test
1 task
This file contains hidden or 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
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.
Fix issue #12371
Description
Improvement of rendering block condition for the Openlayers WMS layer. If an exception is returned in the XML response by geoserver body, the individual image tile is blocked and removed from the queue.
the modified logic is here:
/web/client/components/map/openlayers/plugins/WMSLayer.jsin custom loader:loadFunction()A generic WMS utils has been added
parseOGCExceptionfor exception parsing to display in the console in the event of specific ogc errors.Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
#12371
What is the new behavior?
In the case of exceptions from the geoserver, the attempt to reload the layer is blocked in any case and the specific exception message is displayed in the console
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information
For a complete reproduction of the fix, the production environment where the bug was identified is required, which requires a distribution of the layers on the geoserver via authentication and consistent configuration of the requestsConfigurationRules. See on related issues.