Skip to content
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

[Java][jersey2] Fix serializeToString #6956

Merged
merged 5 commits into from
Jul 23, 2020
Merged

Conversation

wing328
Copy link
Member

@wing328 wing328 commented Jul 16, 2020

To fix #6954

PR checklist

  • Read the contribution guidelines.
  • If contributing template-only or documentation-only changes which will change sample output, build the project beforehand.
  • Run the shell script ./bin/generate-samples.shto update all Petstore samples related to your fix. This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master. These must match the expectations made by your contribution. You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/config/java*. For Windows users, please run the script in Git BASH.
  • File the PR against the correct branch: master
  • Copy the technical committee to review the pull request if your PR is targeting a particular programming language.

cc @bbdouglas (2017/07) @sreeshas (2017/08) @jfiala (2017/08) @lukoyanov (2017/09) @cbornet (2017/09) @jeff9finger (2018/01) @karismann (2019/03) @Zomzog (2019/04) @lwlee2608 (2019/10) @bkabrda (2020/01)

@wing328 wing328 changed the title [Java][jersey2] Fix serializetostring [Java][jersey2] Fix serializeToString Jul 16, 2020
@sebastien-rosset
Copy link
Contributor

sebastien-rosset commented Jul 16, 2020

Fix for #6954

// nulllable and there should be no diffencne as the payload is not null
assertEquals(result, apiClient.serializeToString(pet, null, "application/json", true));

// non-nullable null object should give "" (empty body)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this use case is non trivial to understand because there may be two variants:

  1. The request is supposed to have an empty body by design, i.e. the OpenAPI doc request or response schema indicates the body is empty.
  2. The client or server is setting the data incorrectly. I.e. the OpenAPI doc indicates the object is not nullable, but the actually either the client or server are setting to a null value.

Is it even possible?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The client or server is setting the data incorrectly

This can be prevented by marking the "body" parameter (OAS v2 term) as required.

@wing328 wing328 added this to the 5.0.0 milestone Jul 21, 2020
@wing328 wing328 merged commit 9899315 into master Jul 23, 2020
@wing328 wing328 deleted the fix-jersey2-serializetostring branch July 23, 2020 02:39
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.

[BUG][Java][jersey2] Incorrect serialization of HTTP GET request body
2 participants