[jboss-jira] [JBoss JIRA] Created: (EJBTHREE-844) We need a optimistic locking version of TreeCacheProviderHook
Galder Zamarreno (JIRA)
jira-events at jboss.com
Wed Jan 24 10:47:58 EST 2007
We need a optimistic locking version of TreeCacheProviderHook
-------------------------------------------------------------
Key: EJBTHREE-844
URL: http://jira.jboss.com/jira/browse/EJBTHREE-844
Project: EJB 3.0
Issue Type: Bug
Components: Clustering
Affects Versions: EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Attachments: OptimisticTreeCacheProviderHook.java
Currently, EJB3/Hibernate cannot take advantage of using a second level
cache based in optimistic locking in a EJB3 environment. We only have a
TreeCacheProviderHook CacheProvider for pessimistic locking which
means that if a customer wants to set up optimistic locking, it's forced to
use OptimisticTreeCacheProvider.
However, this class was not designed for managed environments and
ends up creating another cache, so you end up with two caches for the
same job in the same instance which is wrong.
I have created a OptimisticTreeCacheProviderHook which creates an
org.hibernate.cache.OptimisticTreeCache based on the TreeCacheMBean
instance looked up. Please find attached.
This could be improved by creating a accessor method for
TreeCacheProviderHook.cache, so that I can directly extend it rather
than reimplementing CacheProvider. But, I have gone followed the
CacheProvider implementation path so that I can quickly pass a
patched jar containing this class only to the customer for them to try.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list