Nullability issues when having many-to-one associations inside a component

Description

Hi. After upgrading from Hibernate 4.1.3 to 4.3.9 we are getting some weird nullability issues with bidirectional one-to-many associations in a component.
For a working test case see attached ZIP.

The problem seems to be introduced between 4.1.10.Final and 4.1.11.Final -> works with 4.1.10.Final and below but doesn't work as of 4.1.11.Final or above.

Explanation: Parent has a bidirectional one-to-many to Child and Child has a second many-to-one to Parent. The bidirectional one-to-many is managed from the Parent side, the Child side is the inverse side. The unidirectional association to Parent is managed by Child.

Parent:

Child:

When running the test case:

At this stage no queries have been flushed to the database.
When the component is removed and the associations mapped directly in Child:

The test case works without any problem.

Environment

None

Assignee

Unassigned

Reporter

Koen Serneels

Fix versions

None

Labels

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure