[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1921?page=c...
]
Josh Moore commented on HHH-1921:
---------------------------------
Updating to r10347 appears to fix this; at least the given test case now passes. Can
anyone confirm or explain?
"dirty, but no dirty properties" thrown when Interceptor
resets properties.
---------------------------------------------------------------------------
Key: HHH-1921
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1921
Project: Hibernate3
Type: Bug
Components: core
Versions: 3.2.0.cr2
Environment: java version "1.5.0_07"
Hibernate 3.2.cr2
Reporter: Josh Moore
Attachments: InterceptorTest.java, ResetInterceptor.java, dirtybutnotdirty.zip
When Interceptor.onfindDirty() resets properties to their DB value, the check in
DefaultFlushEntityEventListener.scheduleUpdate:
// if it was dirtied by a collection only
int[] dirtyProperties = event.getDirtyProperties();
if ( event.isDirtyCheckPossible() && dirtyProperties==null ) {
if ( !event.hasDirtyCollection() ) {
throw new AssertionFailure("dirty, but no dirty properties");
}
dirtyProperties = ArrayHelper.EMPTY_INT_ARRAY;
}
fails needlessly.
Attached test has been confirmed against SVN TRUNK:
URL:
http://anonhibernate.labs.jboss.com/trunk/Hibernate3
Revision: 10125
--
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