Jira issue originally created by user @guilhermeblanco:
Suppose a situation where:
A -> B
Where the OneToOne unidirectional association contains cascade persist.
If I decide to save an entity B that should create an A instance, it goes into maximum nesting level no matter if I track prePersist or postPersist.
Comment created by @guilhermeblanco:
Failing test case
Uploading a new version, now passing successfully, but consuming the onFlush event (which should not be ideal).
Comment created by @beberlei:
Ah yes, this never worked. The transaction stuff will fix that. You have to use scheduleForInsert() something inside prePersist.
Imported 2 attachments from Jira into https://gist.github.com/e1ed6136e9a69d725eb0