Proxy initialization should be fail-fast when accidentially initializing from event
listeners or interceptor
------------------------------------------------------------------------------------------------------------
Key: HHH-4722
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4722
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.3.2
Environment: Hibernate 3.2.2
Reporter: Joonas Koivunen
Proxy initialization done in event listeners (at least post-update) with an entity that
has a mapped collection seems to result in {code}org.hibernate.AssertionFailure:
collection [role-of-collection] was not processed by flush(){code} at flush time.
By googling up problems like the above assertion failure seems that other people than me
have spent quite a time searching for the origin of this problem; for me it was using a
toString() of an uninitialized proxy.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira