Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-426
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-426
Summary: Enable observation of StaleObjectStateException
Type: New Feature
Status: Unassigned
Priority: Major
Project: Hibernate2
Components:
core
Versions:
2.1 beta 4
Assignee:
Reporter: John Kristian
Created: Mon, 27 Oct 2003 11:46 AM
Updated: Mon, 27 Oct 2003 11:46 AM
Description:
Please enable application software to take action whenever optimistic concurrency control fails (for example, whenever a database change fails because the version of an affected row is different from the version last read). As I understand it, whenever Hibernate detects this it throws a StaleObjectStateException, which is helpful. But StaleObjectStateException might propagate from any one of many Hibernate methods, which makes it difficult for an application to observe it.
I'd like one method in my application to be called whenever Hibernate throws a StaleObjectStateException. (In my application, that method will evict stale entries from the global cache, using an algorithm that's too expensive to execute more frequently.)
A related forum thread: http://forum.hibernate.org/viewtopic.php?t=925032
The Observer pattern (from 'Design Patterns') seems applicable here.
---------------------------------------------------------------------
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
|
