[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2522) Cache Provider implementation for IBM WebSphere's dynamic cache
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2522?page=c...
]
Mike Youngstrom commented on HHH-2522:
--------------------------------------
I noticed you didn't implement the lock and unlock methods. Was this because
Websphere's dynamic cache doesn't provide a locking facility? Or is a locking
facility not needed with dynamic cache? I'm trying to determine if this cache
implementation is going to run into problems with concurrent access.
Cache Provider implementation for IBM WebSphere's dynamic cache
---------------------------------------------------------------
Key: HHH-2522
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2522
Project: Hibernate3
Issue Type: New Feature
Components: core
Affects Versions: 3.2.3
Environment: Hibernate 3.2, IBM WebSphere Application Server version 5.x and 6.x
Reporter: Joris Kuipers
Priority: Minor
Attachments: WebSphereCache.java, WebSphereCacheProvider.java
2nd level cache implementation that uses WebSphere's dynamic cache feature as its
backing implementation.
Using such an implementation is suggested by IBM in articles like
http://www-128.ibm.com/developerworks/websphere/techjournal/0609_alcott/0...,
but I couldn't find an existing implementation. Therefore, I wrote my own.
I briefly documented the usage in the JavaDoc of the Provider implementation.
Info in the dynamic cache itself can be found here:
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/co...
--
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