Skip to content

[Java][JAX-RS] add vendor extension to handle void response in jaxrs-cxf#4158

Merged
wing328 merged 1 commit intoswagger-api:masterfrom
wing328:java_null_response_type
Nov 8, 2016
Merged

[Java][JAX-RS] add vendor extension to handle void response in jaxrs-cxf#4158
wing328 merged 1 commit intoswagger-api:masterfrom
wing328:java_null_response_type

Conversation

@wing328
Copy link
Copy Markdown
Contributor

@wing328 wing328 commented Nov 8, 2016

PR checklist

  • Read the contribution guildelines.
  • Ran the shell/batch script under ./bin/ to update Petstore sample so that CIs can verify the change. (For instance, only need to run ./bin/{LANG}-petstore.sh and ./bin/security/{LANG}-petstore.sh if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates)
  • Filed the PR against the correct branch: master for non-breaking changes and 2.3.0 branch for breaking (non-backward compatible) changes.

Description of the PR

  • Add vendorExtensions.x-java-is-response-void to handle void response in jaxrs-cxf generator.
  • Update pom.xml to cover jaxrs-cxf petstore in Travis CI.

@wing328 wing328 added this to the v2.2.2 milestone Nov 8, 2016
@wing328 wing328 merged commit 68e1afd into swagger-api:master Nov 8, 2016
@wing328 wing328 deleted the java_null_response_type branch November 8, 2016 13:42
davidgri pushed a commit to davidgri/swagger-codegen that referenced this pull request May 11, 2017
[Java][JAX-RS] add vendor extension to handle void response in jaxrs-cxf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant