Skip to content

Issue 2495: response handling for multi link request #2496

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

Conversation

anayonkars
Copy link

This PR is to solve issue 2495.

It handles correction of error codes for single association resource. However, it doesn't (yet) handles multiple association resource.

  • You have read the Spring Data contribution guidelines.
  • You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
  • You submit test cases (unit or integration tests) that back your changes.
  • You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

In RepositoryPropertyReferenceController, handled response code for empty links.
Instead of IllegalArgumentException and HTTP 500, now it throws HttpMessageNotReadableException and HTTP 400

Signed-off-by: Anayonkar Shivalkar <anayonkar.shivalkar@gmail.com>
In RepositoryPropertyReferenceController, handled response code for multiple links.
Instead of IllegalArgumentException and HTTP 500, now it throws HttpMessageNotReadableException and HTTP 400

Signed-off-by: Anayonkar Shivalkar <anayonkar.shivalkar@gmail.com>
In RepositoryPropertyReferenceController, handled response code where no links are sent (List of Map).
Instead of IllegalArgumentException and HTTP 500, now it throws HttpMessageNotReadableException and HTTP 400

Signed-off-by: Anayonkar Shivalkar <anayonkar.shivalkar@gmail.com>
Fixed test cases

Signed-off-by: Anayonkar Shivalkar <anayonkar.shivalkar@gmail.com>
@anayonkars anayonkars closed this Jun 29, 2025
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.

1 participant