The following comment has been added to this issue:
Author: Gavin King
Created: Wed, 16 Jul 2003 9:47 AM
Body:
This was an intentional change made because *everyone* wanted to be able to "resave" deleted objects.
I'm not sure what a good solution to your problem is.
Why not just track deleted objects in your own collection, from onDelete()
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-191
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-191
Summary: Cannot now get postFlush on deletes
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0.1
Assignee:
Reporter: Keith Manning
Created: Mon, 14 Jul 2003 9:43 AM
Updated: Mon, 14 Jul 2003 9:43 AM
Description:
In v1.2 we listened to onSave, onDelete & then on postFlush when we updated a listening form - this fixed a bug where we were updating the listening form even if commit failed. Now we've upgraded to 2.0 we see that in SessionImpl.postDelete the entitiesByKey is now deleted, so our listener never gets notified that the object has been successfully deleted in the interceptor.postFlush() call - i.e. the object is no longer in the entities iterator.
We believe that we are correctly using the interceptor object & I cannot see a workaround - if we are then this is a bug, but if not how should we be listening to these persistence events?
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
