-
Notifications
You must be signed in to change notification settings - Fork 1.1k
DATAMONGO-1271 Provide read lifecycle events when loading DBRefs #322
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
This reverts commit 7b27368.
BTW my CLA code is 121620150519031801 |
We now check properties for their usage as ctor arguments, that might already have been resolved, before setting the actual value. This prevents turning already eagerly fetched DBRefs back into LazyLoadingProxies. Relates to original PR #322.
@yacota I've created #335 to separate DATAMONGO-1287 (the issue with lazy dbref values in ctor) from DATAMONGO-1271. Once that's solved I'll take care about this one here. Thanks already! |
… arguments. As per discussion on the ticket we now omit looking up the value for an association being used as constructor argument as the simple check whether the currently handled property is a constructor argument is sufficient to potentially skip handling the value. Related pull requests: #335, #322.
… arguments. As per discussion on the ticket we now omit looking up the value for an association being used as constructor argument as the simple check whether the currently handled property is a constructor argument is sufficient to potentially skip handling the value. Related pull requests: #335, #322.
… arguments. As per discussion on the ticket we now omit looking up the value for an association being used as constructor argument as the simple check whether the currently handled property is a constructor argument is sufficient to potentially skip handling the value. Related pull requests: #335, #322.
@christophstrobl DATAMONGO-1287 was closed a long time ago but DATAMONGO-1271 is still "work in progress". Can I do anything to speed up things?, maybe this feature is finally discarded? ... I would really like to have feedback about it (I know all the team is pretty busy working on new things) |
We now publish livecycle events when loading DBRefs. Original Pull Request: #322 CLA: 121620150519031801 (Jordi Llach Fernandez)
Removed non Java 6 language features, reworked and added a few tests. Original Pull Request: #322
While checking the original PR you've seen that in the original PR I assumed that lazy DBRef when used in constructor should be skipped(non resolved), as we discussed in https://jira.spring.io/browse/DATAMONGO-1287 that is not the desired behaviour and resolving them eagerly was preferred. |
Removed non Java 6 language features, reworked and added a few tests. Original Pull Request: #322
We now publish livecycle events when loading DBRefs. Original Pull Request: #322 CLA: 121620150519031801 (Jordi Llach Fernandez)
Removed non Java 6 language features, reworked and added a few tests. Original Pull Request: #322
@christophstrobl to me it's 👍 |
We now publish livecycle events when loading DBRefs. Original Pull Request: #322 CLA: 121620150519031801 (Jordi Llach Fernandez)
Removed non Java 6 language features, reworked and added a few tests. Original Pull Request: #322
You're welcome @christophstrobl |
We now publish livecycle events when loading DBRefs. Original Pull Request: #322 CLA: 121620150519031801 (Jordi Llach Fernandez)
Removed non Java 6 language features, reworked and added a few tests. Original Pull Request: #322
The PR was for 1271 initially but then found 1287