DATAJPA-562 - Support for pluggable generic post-processing of JPA Query results. #99
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
…ery results. Prepare issue branch.
thomasdarimont
pushed a commit
that referenced
this pull request
Jun 26, 2014
…ery results. We introduced the JpaResultPostProcessor interface to provide the infrastructure to be able to post-process the results of entityManager.getResultList() or entityManager.getSingleResult() invocations. This enables us to manipulate the results like automatically detaching them from the PersistenceContext or masking values etc via pluggable strategies. By default a NoopJpaResultPostProcessor is used that returns the results as is. We also provide a DetachingJpaResultPostProcessor that detaches all returned domain-objects from the associated persistence-context. Original pull request: #99.
…ery results. We introduced the JpaResultPostProcessor interface to provide the infrastructure to be able to post-process the results of entityManager.getResultList() or entityManager.getSingleResult() invocations. This enables us to manipulate the results like automatically detaching them from the PersistenceContext or masking values etc via pluggable strategies. By default a NoopJpaResultPostProcessor is used that returns the results as is. We also provide a DetachingJpaResultPostProcessor that detaches all returned domain-objects from the associated persistence-context. Original pull request: #99.
|
Why was this closed? This is such an invaluable thing for me to have in my project. It's freaking impossible to have a clean usable interceptor to a repository without having to use AOP which just causes headache and unnecessary typing. |
|
Hi @RobzInadE, here is some additional context: https://jira.spring.io/browse/DATAJPA-562 Cheers, |
|
I see. I tested your solution, however calls to non-implemented "magical" repository methods were not caught in any of the SimpleJpaRepository class. I kind of need something like this in my project like I said. Have you got any other ideas of implementing a similar solution (that also applies to repository methods) ? Regards |
This pull request was closed.
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.
We introduced the JpaResultPostProcessor interface to provide the infrastructure to be able to post-process the results of entityManager.getResultList() or entityManager.getSingleResult() invocations.
This enables us to manipulate the results like automatically detaching them from the PersistenceContext or masking values etc via pluggable strategies.
By default a NoopJpaResultPostProcessor is used that returns the results as is. We also provide a DetachingJpaResultPostProcessor that detaches all returned domain-objects from the associated persistence-context.