Axis ordering issue in WMSClient #2
Merged
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
…y checking axis order against urn based crs
… as default WMS version
|
I'm pulling this into master now, as it fixes build issues on jenkins. |
hwbllmnn
added a commit
that referenced
this pull request
Dec 4, 2012
fixed axis ordering issue in WMSClient, build problems
stempler
referenced
this pull request
in stempler/deegree3
Sep 1, 2017
fix null pointer exception for requests when style is null
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 request fixes http://tracker.deegree.org/deegree-services/ticket/469 (axis ordering issue when using WMSClient with version 1.3.0).
Additionaly, to show the bug is fixed, I've adapted the deegree-compliance-tests workspaces' RemoteWmsTileStore to use EPSG:4326 again, which resulted in an error before.
(this pull request includes the commits from #1)