CascadeEntityJoinWalker.isTooManyCollections() causes random behavior

Description

CascadeEntityJoinWalker.isTooManyCollections() depends on the current state of JoinWalker.associations to decide if to add the association. This causes a behavior depending on the order of the result of persister.getSubclassPropertyType() in JoinWalker.walkEntityTree() (in effect, only the first eligible association will be added.)

Unfortunately, the order of the result of persister.getSubclassPropertyType() can be random (is not fixed) in the scan process (MetadataBuildingProcess.prepare() and ScanningCoordinator.coordinateScan().)

In all, this causes a mysterious "Unable to resolve property" exception in some run config and not the others.

Environment

None

Activity

Show:
Gail Badner
January 4, 2017, 8:26 PM

Please attach a runnable test case that reproduces your issue. You can find test templates at https://github.com/hibernate/hibernate-test-case-templates.

zhiwei wei
March 9, 2017, 3:02 AM

I found that my problem was caused by an error in our entity annotation. Sorry for the false alarm, can we close this now?

Assignee

Unassigned

Reporter

zhiwei wei

Fix versions

None

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Affects versions

Priority

Major
Configure