[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-5478) Update Ehcache capabilities in the section [21.2. The Second Level Cache] of the documentation

[Strong Liu (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Strong Liu resolved HHH-5478.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 3.6.6
         Assignee: Strong Liu

applied pull request https://github.com/hibernate/hibernate-core/pull/133

but we also need fix this in 4.0, open a new jira

> Update Ehcache capabilities in the section [21.2. The Second Level Cache] of the documentation
> ----------------------------------------------------------------------------------------------
>
>                 Key: HHH-5478
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5478
>             Project: Hibernate Core
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Pascal Thivent
>            Assignee: Strong Liu
>            Priority: Minor
>             Fix For: 3.6.6
>
>
> According to the [Hibernate Second Level Cache|http://ehcache.org/documentation/hibernate.html] documentation on the Ehcache website, Ehcache 2.0+ is cluster safe:
> {quote}
> h3. [Is Ehcache Cluster Safe?|http://ehcache.org/documentation/hibernate.html#Is_Ehcache_Cluster_Safe]
> hibernate.org maintains a table listing the providers. While ehcache works as a distributed cache for Hibernate, it is not listed as "Cluster Safe". What this means is that `Hibernate's lock and unlock methods are not implemented. Changes in one node will be applied without locking. This may or may not be a noticeable problem.
> In Ehcache 1.7 when using Terracotta, this cannot happen as access to the clustered cache itself is controlled with read locks and write locks.
> In Ehcache 2.0 when using Terracotta, the lock and unlock methods tie-in to the underlying clustered cache locks. We expect Ehcache 2.0 to be marked as cluster safe in new versions of the Hibernate documentation.
> {quote}
> And as of Ehcache 2.1.0, Ehcache now supports the transactional strategy. From the [JPA|http://ehcache.org/documentation/jta.html] page:
> {quote}
> h3. Hibernate Transactions
> Ehcache is a "transactional" cache for Hibernate purposes. The <<<net.sf.ehcache.hibernate.EhCacheRegionFactory>>>
> has support for Hibernate entities configured with <cache usage="transactional"/>.
> {quote}
> Shouldn't the cache provider table of the section [21.2. The Second Level Cache|http://docs.jboss.org/hibernate/core/3.6/reference/en-US/html/performance.html#performance-cache] and the cache compatibility matrix of the section [21.2.6. Cache-provider/concurrency-strategy compatibility|http://docs.jboss.org/hibernate/core/3.6/reference/en-US/html/performance.html#performance-cache-compat-matrix] be updated to reflect this (or at least make it clear that this is possible, be it through third party support)?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira