Details
-
Task
-
Resolution: Fixed
-
Critical
-
7.0.1
-
1
-
CX Sprint 257
Description
While serializable anonymous inner classes are traditionally considered "bad", we consider these safe assuming certain conditions are met:
- only one anonymous class of a given type[1] per enclosing class
- OR each anonymous class has a non-trivial (e.g. natural) serialVersionUID, which is unique within the enclosing class
For dot releases, in addition to ensuring the serialVersionUID does not change, and that serializable classes are not added nor removed, an added check must ensure that [1] does not change for serializable anonymous inner classes.
Attachments
Issue Links
- relates to
-
MB-45812 [CX] eliminate "unsafe" serializable anonymous inner classes
- Resolved