[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582?page=c...
]
Marco Pozzato commented on HHH-1582:
------------------------------------
The simpler way, to me, is adding a "success" boolean to Post-*-Event: Would you
accept such a patch?
Or are there some problem in such a solution?
PostInsertListener + "post-commit-insert"
-----------------------------------------
Key: HHH-1582
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582
Project: Hibernate3
Issue Type: Bug
Affects Versions: 3.1.2
Reporter: Daniel Gredler
Assignee: Emmanuel Bernard
Fix For: 3.3
Original Estimate: 3 hours
Remaining Estimate: 3 hours
I'm using a custom PostInsertEventListener mapped to the
"post-commit-insert" event to process domain objects. However,
PostInsertEventListener's onPostInsert(PostInsertEvent) is getting called even when
the insert was not successful (ie, due to a unique constraint in the database or some
such). It looks to me like Hibernate should either a) not invoke the event listener if the
insert failed or b) provide state (perhaps in the form of a boolean indicating
success/failure). Personally I'd rather the method not be called on failure, but there
may be use cases out there for the second option.
As an example, it looks like Hibernate's own LuceneEventListener will add a domain
object to the index in onPostInsert(PostInsertEvent) even if the insert failed.
Note that this problem also seems to exist in EntityDeleteAction and EntityUpdateAction
(which would mean that Hibernate's LuceneEventListener removes domain objects from the
Lucene index even if the delete fails!).
--
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