[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2522) Cache Provider implementation for IBM WebSphere's dynamic cache

[prasenjit B (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28012 ] 

prasenjit B commented on HHH-2522:
----------------------------------

Thanks Joris,
At this point I have two Concerns 
1.We can not use CMTTransactionFactory and webSphereExtendedJTATransation factory  for the configuration.If we do that we get error with synchronization issues with Save or Update operations.We have used .However using org.hibernate.transaction.WebSphereTransactionManagerLookup 
 and org.hibernate.transaction.JTATransactionFactory  ,we could eleminate such issues.will there be any problem related to the performance if we don't use the former combination?If yes ,How do we eleminate that?

2.I would like to implement the 2nd level cache to check if such problems are eleminated.To start with ,I have included two classes of yours in my application.What chages do I need to do for the Hibernate config and the hbms to to include the 2nd level cache support using WebSphere's dynamic cache ?

Regards

> 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/0609_alcott.html, 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=/com.ibm.websphere.base.doc/info/aes/ae/tdyn_distmap.html

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira