Skip to content

DBref lazy falls back to eager in case of no default constructor [DATAMONGO-1402] #2315

Open
@spring-projects-issues

Description

@spring-projects-issues

Paul Sterl opened DATAMONGO-1402 and commented

During the fix of the wrong validation using DBRef I discovered that apparently lazy will silently converted to eager if no default no-arg constructor could be found.

This can easily be reproduced using by pull request:
#350

And remove the default constructor from the Address class --> unit test will fail as I added an assert to ensure the LazyProxy is used.

I would suggest to check some other cases too to make sure it works in the most default cases


Affects: 1.8.4 (Gosling SR4)

Metadata

Metadata

Assignees

Labels

in: mappingMapping and conversion infrastructuretype: bugA general bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions