Skip to content

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

Closed
wants to merge 2 commits into from
Closed

DATAMONGO-1271 Provide read lifecycle events when loading DBRefs #322

wants to merge 2 commits into from

Conversation

yacota
Copy link
Contributor

@yacota yacota commented Sep 16, 2015

The PR was for 1271 initially but then found 1287

@yacota
Copy link
Contributor Author

yacota commented Sep 17, 2015

BTW my CLA code is 121620150519031801

christophstrobl added a commit that referenced this pull request Nov 19, 2015
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.
@christophstrobl
Copy link
Member

@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!

christophstrobl added a commit that referenced this pull request Nov 20, 2015
…onstructor.

We now check properties for their usage as constructor arguments, that might already have been resolved, before setting the actual value. This prevents turning already eagerly fetched DBRefs back into LazyLoadingProxies.

Original pull request: #335.
Related pull request: #322.
christophstrobl added a commit that referenced this pull request Nov 20, 2015
…onstructor.

We now check properties for their usage as constructor arguments, that might already have been resolved, before setting the actual value. This prevents turning already eagerly fetched DBRefs back into LazyLoadingProxies.

Original pull request: #335.
Related pull request: #322.
christophstrobl added a commit that referenced this pull request Nov 20, 2015
…onstructor.

We now check properties for their usage as constructor arguments, that might already have been resolved, before setting the actual value. This prevents turning already eagerly fetched DBRefs back into LazyLoadingProxies.

Original pull request: #335.
Related pull request: #322.
@yacota yacota changed the title Datamongo 1271 and Datamongo 1287 Datamongo 1271 (Datamongo 1287 --> https://github.com/spring-projects/spring-data-mongodb/pull/335) Nov 20, 2015
@yacota yacota changed the title Datamongo 1271 (Datamongo 1287 --> https://github.com/spring-projects/spring-data-mongodb/pull/335) Datamongo 1271 Nov 20, 2015
odrotbohm added a commit that referenced this pull request Nov 23, 2015
… 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.
odrotbohm added a commit that referenced this pull request Nov 23, 2015
… 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.
odrotbohm added a commit that referenced this pull request Nov 23, 2015
… 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.
@yacota yacota changed the title Datamongo 1271 DATAMONGO-1271 Provide read lifecycle events when loading DBRefs Mar 4, 2016
@yacota
Copy link
Contributor Author

yacota commented May 11, 2016

@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)

christophstrobl pushed a commit that referenced this pull request May 24, 2016
We now publish livecycle events when loading DBRefs.

Original Pull Request: #322
CLA: 121620150519031801 (Jordi Llach Fernandez)
christophstrobl added a commit that referenced this pull request May 24, 2016
Removed non Java 6 language features, reworked and added a few tests.

Original Pull Request: #322
@yacota
Copy link
Contributor Author

yacota commented May 24, 2016

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.
But let me point to the issue https://jira.spring.io/browse/DATAMONGO-1332 where because of this and the way MappingMongoConverter uses ObjectPath could cause a StackOverFlow error under certain circumstances
Thanks @christophstrobl

christophstrobl added a commit that referenced this pull request May 24, 2016
Removed non Java 6 language features, reworked and added a few tests.

Original Pull Request: #322
christophstrobl pushed a commit that referenced this pull request May 25, 2016
We now publish livecycle events when loading DBRefs.

Original Pull Request: #322
CLA: 121620150519031801 (Jordi Llach Fernandez)
christophstrobl added a commit that referenced this pull request May 25, 2016
Removed non Java 6 language features, reworked and added a few tests.

Original Pull Request: #322
@christophstrobl
Copy link
Member

@yacota I saw the constructor argument related changes and modified the PR a bit - here's issue branch in case you want to have a look before I port the stuff to master.

@yacota
Copy link
Contributor Author

yacota commented May 25, 2016

@christophstrobl to me it's 👍

christophstrobl pushed a commit that referenced this pull request May 27, 2016
We now publish livecycle events when loading DBRefs.

Original Pull Request: #322
CLA: 121620150519031801 (Jordi Llach Fernandez)
christophstrobl added a commit that referenced this pull request May 27, 2016
Removed non Java 6 language features, reworked and added a few tests.

Original Pull Request: #322
@christophstrobl
Copy link
Member

thanks @yacota . Merged via d1251c4.

@yacota
Copy link
Contributor Author

yacota commented May 27, 2016

You're welcome @christophstrobl

christophstrobl pushed a commit that referenced this pull request May 27, 2016
We now publish livecycle events when loading DBRefs.

Original Pull Request: #322
CLA: 121620150519031801 (Jordi Llach Fernandez)
christophstrobl added a commit that referenced this pull request May 27, 2016
Removed non Java 6 language features, reworked and added a few tests.

Original Pull Request: #322
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.

2 participants