[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5303?page=c...
]
Paul Bakker commented on HHH-5303:
----------------------------------
I did another test.
@Cacheable(true)
No @Cache
The only cache related setting in Persistence.xml:
{code}
<property name="javax.persistence.sharedCache.mode"
value="ENABLE_SELECTIVE"/>
{code}
After executing the determineCacheSettings the cacheAnn instance is as follows:
region = "demo.entities.Employee"
usage = "NONE"
That seems to be wrong. How does it figure out the cacheconcurrencyStrategy? That
shouldn't be NONE by default because that defeats the purpose of having a standardized
@Cacheable annotation.
@Cachable has no effect
-----------------------
Key: HHH-5303
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5303
Project: Hibernate Core
Issue Type: Bug
Components: caching (L2), entity-manager
Affects Versions: 3.5.2
Environment: Tested on HSQL (included in testcase) and MySQL database
Reporter: Paul Bakker
Attachments: testcase.zip
The JPA 2.0 @Cachable annotation has no effect at all. Just putting @Cachable on a class
is not enough to enable caching. You must also configure a concurrency strategy with
either @Cache or a hibernate.ejb.classcache setting in persistence.xml.
If those settings are in place, @Cacheble still has no effect. Entities are cached, but
@Cachable(false) doesn't change this behavior.
I included a Maven example project that tests this behavior. The project has two profiles
to switch between Hibernate and EclipseLink:
mvn -P hibernate clean test
mvn -P eclipselink clean test
--
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