-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution:
Won't Fix
-
Affects Version/s: EAP 5.0.0.CR4 (FCS and BETA2), EAP 5.0.0.CR5, EAP 5.0.0
-
Fix Version/s: TBD EAP 5
-
Component/s: Hibernate
-
Labels:None
-
Affects:Release Notes
-
Workaround:Workaround Exists
-
Workaround Description:
-
Release Notes Docs Status:Not Required
The API contract for EntityRegionAccessStrategy.evict(Object) and CollectionRegionAccessStrategy.evict(Object) states that an item should be forcibly evicted from the cache immediately, without regard for transaction isolation. The Hibernate/JBoss Cache integration does not implement this properly because the JBC removeNode() calls it makes do not deal with transactional issues.
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4517
- cloned to
-
JBPAPP-5550 Document - HHH-4517 Hibernate/JBC integration doesn't property handle Entity/CollectionRegionAccessStrategy evict(Object)
-
- Closed
-
- is related to
-
JBPAPP-2957 HHH-3818 Hibernate/JBC integration doesn't property handle Entity/CollectionRegionAccessStrategy evict
-
- Closed
-