A Mutable annotation can be used on a Basic mapping.
It can be used on complex field types to indicate that the value itself can be changed or not changed (instead of being replaced).
Most basic types are not mutable, i.e. int, long, float, double, String, BigDecimal.
Date or Calendar types are assumed not to be mutable by default, if it is desired to call
the set methods on the Date or Calendar, then the mapping must be set to be Mutable.
For Date and Calendar types the global persistence property "eclipselink.temporal.mutable" can also be set to "true".
For serialized types, by default they are assumed to be mutable, if they are not mutable this annotation can be set to "false".
Mutable basic mappings affect the overhead of change tracking, attribute change tracking can only be woven with non-mutable mappings.
-
Optional Element Summary
Optional ElementsModifier and TypeOptional ElementDescriptionbooleanSet the mapping to be mutable, or not mutable.
-
Element Details
-
value
boolean valueSet the mapping to be mutable, or not mutable.- Default:
true
-