-
Couldn't load subscription status.
- Fork 563
DATAREST-836 Provide ability to handle 'after' Http findOne event #213
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
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
@odrotbohm
odrotbohm
force-pushed
the
master
branch
from
September 21, 2016 06:08
6c68355 to
8492063
Compare
pivotal-issuemaster
commented
Jan 9, 2017
@varpa89 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
pivotal-issuemaster
commented
Jan 9, 2017
@varpa89 Thank you for signing the Contributor License Agreement!
@odrotbohm
odrotbohm
force-pushed
the
master
branch
from
January 24, 2017 15:58
6113dfe to
5494f1f
Compare
@schauder
schauder
force-pushed
the
master
branch
from
March 30, 2017 08:36
729309b to
b9957d1
Compare
@spring-projects-issues
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged
label
Jan 4, 2021
@odrotbohm
odrotbohm
force-pushed
the
main
branch
3 times, most recently
from
September 21, 2021 15:03
63ac127 to
cfb7079
Compare
@odrotbohm
odrotbohm
force-pushed
the
main
branch
from
March 23, 2022 10:49
42c7add to
e656c89
Compare
@gregturn
gregturn
force-pushed
the
main
branch
from
March 30, 2023 15:37
0ebe878 to
48aa76e
Compare
@odrotbohm
odrotbohm
force-pushed
the
main
branch
from
September 2, 2025 12:08
555321c to
1c27b81
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
At the moment to read item resource by ID spring data rest uses JPA repository 'findOne' method.
There are some different use cases to use this method:
In some use cases we need
Provide security via findOne in some cases make different troubles (deserialization an entity to object by ID) and may be unnecessary.
In this issue I suggest to implement HandleAfterFindOne annotation and AfterFindOneEvent event and publish them in RepositoryEntityController. So we could use annotated handlers