[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2522?page=c...
]
Joris Kuipers commented on HHH-2522:
------------------------------------
AFAIK the WebSphere cache is responsible for doing locking, there's no need to add
this yourself. It would also be nearly impossible, since this is a distributed object,
therefore synchronizing in your local JVM is not enough. The IBM documentation has very
little detail on this: if you want to make sure, you can decompile the classes in the
com.ibm.ws.cache package and have a look (note: not the com.ibm.websphere.cache package,
that only holds the public API). On WAS 6.1, you can find these classes in
plugins\com.ibm.ws.runtime_6.1.0.jar.
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