Preserve response data on error. RESTClient still has response data for HTTP >= 400 status#9
Open
michaelcameron wants to merge 1 commit intoGrailsrocks:masterfrom
Open
Conversation
…or HTTP >= 400 status
Member
|
Is there a JIRA for this issue? |
Contributor
Author
|
I don't believe so, no |
|
You could also make the RESTClient always use the defaultSuccessHandler in case it's not required to have the ContentChangedEvent have a different evensSource when status >= 400.
|
christoph-frick
pushed a commit
to christoph-frick/grails-functional-test
that referenced
this pull request
Mar 24, 2015
small improvements in the create-functional-test script
|
Please make this happen! private void assertResponseContains(containText) { |
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.
There's still data in HTTP responses >= 400. RESTClient will preserve that data and then throw the exception. I know this is duplicate code for the try, so ripe for refactoring. I tried playing around with failure handlers. I want to do what RESTClient.defaultFailureHandler() without throwing the exception, but it relies on HTTPBuilder.defaultSuccessHandler() which is protected and non-trivial. The only clean way I can think of would be to subclass RESTClient and override defaultFailureHandler, then having access to HTTPBuilder.defaultSuccessHandler(). I know you have the TODO in there to change/remove the failure handler. If you want to go down that route. I could make the changes and submit a pull request.