[hibernate-issues] [Hibernate-JIRA] Resolved: (EJB-180) org.hibernate.AssertionFailure: dirty, but no dirty properties
Emmanuel Bernard (JIRA)
noreply at atlassian.com
Mon Aug 28 19:38:25 EDT 2006
[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-180?page=all ]
Emmanuel Bernard resolved EJB-180:
----------------------------------
Resolution: Won't Fix
Really seems to be a core issue, (see the core related bug), So I close this one to prevent dupe effort
> org.hibernate.AssertionFailure: dirty, but no dirty properties
> --------------------------------------------------------------
>
> Key: EJB-180
> URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-180
> Project: Hibernate Entity Manager
> Type: Bug
> Environment: JBoss 4.0.4CR2
> Reporter: Michał Borowiecki
>
>
> This exception is raised in the following scenario:
> 1. An entity is returned from a find operation.
> 2. It is modified.
> 3. EntityManager.merge is called on it.
> 4. In the PreUpdate callback the bean has its fields modified to the values they had before step 2.
> 5. The DefaultFlushEntityEventListener determines that all the fields have their values equal to those in the cache and raises the error:
> org.hibernate.AssertionFailure: dirty, but no dirty properties
> at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:256)
> at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:121)
> at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:195)
> at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76)
> at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26)
> at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:988)
> at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:337)
> at org.hibernate.ejb.AbstractEntityManagerImpl$1.beforeCompletion(AbstractEntityManagerImpl.java:473)
> This bug is probably a reincarnation of EJB-29, however that report did not have a comprehensive description so I decided to create a new one.
--
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.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list