An error should be raised when a persistent field comes with inline mutable object initialization, cause the result is very surprised: the field is not in session boundary, instead visible by all requests. The bad thing is this kind of code can pass unit tests and integration tests without any warnings.
A document is good for this issue, but it's not enough; it's hard to guarantee every developer have read that piece of ducument carefully.
|Summary||A persistent field with inline mutable object initialization should not be allowed.||Fields marked with @Persist should not allow default values|
|Resolution||Fixed [ 1 ]|
|Assignee||Howard M. Lewis Ship [ hlship ]|
|Fix Version/s||5.0.16 [ 12313427 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|