Parse out of order ListBucket response elements #189
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
Currently, jclouds assumes that the <ID> must occur before the <DisplayName> tag. If the XML body does not adhere to this order, the parser throws a NullPointerException. Scaleway is a cloud provider that does not adhere to this order and returns the <DisplayName> tag before the <ID> tag. The patch changes the parser to not depend on the order of the tags. See commit 04feb8f for a similar fix
|
Thank you for your contribution @mlanoe! |
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.
Currently, jclouds assumes that the "ID" must occur before the "DisplayName" tag. If the XML body does not adhere to this order, the parser throws a NullPointerException.
Scaleway is a cloud provider that does not adhere to this order and returns the "DisplayName" tag before the "ID" tag. The patch changes the parser to not depend on the order of the tags.
See commit 04feb8f for a similar fix