swagger-api / swagger-api/swagger-codegen

[JAVA] Client generation - issue with okhttp version 2.7.4 - getResponse TODO

Open
#7,193 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

JAVA Client generation
Server is Spring Data Rest with JPA Simple repositories - with Springfox Swagger annotations.

Generated client is not properly deserializing.

Swagger-codegen version

2.2.3

Swagger declaration file content or url
Command line used for generation

java -jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar generate -i C:\swagger.yaml -l java -o C:\generated_java_client

Steps to reproduce
  1. Create Swagger using Springfox on top of Spring Data Rest Repositories
  2. Generate Java client using Swagger Codegen
  3. Test the generated client against server

Response body is always empty in the client side, regardless of acutal server response.

Related issues/PRs
Suggest a fix/enhancement

Problems seems in the fields:
@SerializedName("content")
@SerializedName("links")

Actual names should be:
_embedded
_links

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Java generation command shown in the issue and inspect the generated client models and response deserialization. Compare the generated @SerializedName("content") and @SerializedName("links") fields with the server response, including _embedded and _links. Done means the generated client deserializes the actual response body instead of returning it empty.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
api, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.