Skip to content

[Java jersey2 okhttp-gson] Fix compilation error, record status code and response headers of last request #1215

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Sep 11, 2015

Conversation

xhh
Copy link
Contributor

@xhh xhh commented Sep 11, 2015

  • Fix compilation error in the jersey2 template regarding binary support
    Binary input & output support was added to the default Java client codegen (see PR support binary input and output #1124) which changed the signature of the invokeAPI method in "api.mustache", causing the "jersey2" client fail to compile. Here an separate version of api.mustache is added for "jersey2" client which does not handle binary support (for now).
  • Record (allow access to) status code and response headers of last request in Java clients generated with the jersey2 and okhttp-gson library templates (it has been done for the default template in PR Add status code and response headers of the last request to java and c# #1127).
  • Rebuild Java clients for the petstore sample

xhh added 4 commits September 11, 2015 13:22
Binary parameter/response support was added to the default Java client
codegen which changed the signature of the `invokeAPI` method in
"api.mustache", causing the "jersey2" client fail to compile.
Here an separate version of `api.mustache` is added for "jersey2" client
which does not handle binary support (for now).
wing328 added a commit that referenced this pull request Sep 11, 2015
[Java jersey2 okhttp-gson] Fix compilation error, record status code and response headers of last request
@wing328 wing328 merged commit 46f78f2 into swagger-api:master Sep 11, 2015
@fehguy fehguy modified the milestone: v2.1.4 Oct 26, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants