Changes to fields marked as non-updateable written to L2 cache
--------------------------------------------------------------
Key: HHH-2781
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2781
Project: Hibernate3
Issue Type: Bug
Components: caching (L2)
Reporter: Steve Ebersole
Assignee: Steve Ebersole
When the value a field marked as update="false" is changed, that changed state
is written to the L2 cache. This occurs at least on reattachment, but I assume it also
occurs for managed entities (need to verify).
Viable solutions include:
1) disallow this combination (cached + non-updateable, non-generationed properties)
2) implicitly treat these properties as generated.
Workaround is to mark these fields as generated.
--
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