-
Bug
-
Resolution: Delivered
-
P4
-
None
-
team
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8342351 | 24 | Valerie Peng | P4 | Resolved | Fixed | b20 |
JDK-8331278 | 23.0.2 | Prasadarao Koppula | P4 | Resolved | Fixed | b02 |
JDK-8349986 | 21.0.7 | Goetz Lindenmaier | P4 | Resolved | Fixed | b03 |
JDK-8332588 | 21.0.5-oracle | Prasadarao Koppula | P4 | Resolved | Fixed | b01 |
JDK-8350681 | 17.0.15 | Goetz Lindenmaier | P4 | Resolved | Fixed | b04 |
JDK-8331273 | 17.0.13-oracle | Prasadarao Koppula | P4 | Resolved | Fixed | b01 |
JDK-8331274 | 11.0.25-oracle | Prasadarao Koppula | P4 | Resolved | Fixed | b01 |
JDK-8331276 | 8u431 | Prasadarao Koppula | P4 | Resolved | Fixed | b04 |
Essentially, deserialization is a form of object construction and should enforce the same data validation and consistency checks as enforced by the constructor(s). Thus, additional checks may be needed when deserializing the objects to ensure that values failing the constructor check are rejected during deserialization as well.
- backported by
-
JDK-8331273 Serialization considerations
-
- Resolved
-
-
JDK-8331274 Serialization considerations
-
- Resolved
-
-
JDK-8331276 Serialization considerations
-
- Resolved
-
-
JDK-8331278 Serialization considerations
-
- Resolved
-
-
JDK-8332588 Serialization considerations
-
- Resolved
-
-
JDK-8342351 Serialization considerations
-
- Resolved
-
-
JDK-8349986 Serialization considerations
-
- Resolved
-
-
JDK-8350681 Serialization considerations
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk17u-dev/ae0177b6
-
Commit(master) openjdk/jdk21u-dev/17cb53a9
-
Review(master) openjdk/jdk17u-dev/3278
-
Review(master) openjdk/jdk21u-dev/1391