[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5303?page=c...
]
Steve Ebersole commented on HHH-5303:
-------------------------------------
And which cache provider have you specified?
For reference here is the code "in play":
http://fisheye.jboss.org/browse/Hibernate/core/branches/Branch_3_5/annota...
Basically if only @Cache is specified it looks to the cache provider you have configured:
determineCacheConcurrencyStrategy()
@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