Introduced client module, abstracting commons away from jersey/apache #27
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
|
Thank you Steven. I'll merge your changes. I might do some minor changes but I like you additions. I will also update the RestEasy integration to make use of the new client module code. This should remove inconsistencies between implementations. |
kristofa
added a commit
that referenced
this pull request
Jul 20, 2014
Introduced client module, abstracting commons away from jersey/apache
Closed
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.
I refactored out common code into a brave-client module, and updated the tests and implementations of jersey and apache accordingly. I also included the ability to override what the service name is, since not all service names can be derived from the first part of a URI path.
Fixes #24