[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4517?page=c...
]
Brian Stansberry updated HHH-4517:
----------------------------------
Fix Version/s: (was: 3.5)
Removing from the 3.5 schedule as I don't see a good fix for this. It basically
requires a separate communication channel, or some ability to send custom commands through
the JBC RpcDispatcher (which JBC does not support.)
Hibernate/JBC integration doesn't property handle
Entity/CollectionRegionAccessStrategy evict(Object)
-----------------------------------------------------------------------------------------------------
Key: HHH-4517
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4517
Project: Hibernate Core
Issue Type: Bug
Components: caching (L2)
Affects Versions: 3.3.2, 3.5.0.Beta-1
Reporter: Brian Stansberry
Assignee: Brian Stansberry
See HHH-3818 for a full discussion of the general issue. This JIRA deals with the
evict(Object) case, as opposed to evictAll(). The solution is a bit more complex as it
requires checking not just whether the entire region has been invalidated, but also
particular keys.
--
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