Java Object Serialization Specification¶
Oracle. Java Object Serialization Specification.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Boundary State Loss
- In computing, state serialization across a process or network boundary cannot transmit closures, open descriptors, or runtime-only objects, and microservice migrations regularly discover state that lived in the monolith and did not survive the split.
This sourceOracle/Sun Microsystems. Specifies that runtime-only entities — open sockets, file descriptors, threads, and other non-serializable references — cannot be marshalled and must be marked transient (yielding NotSerializableException or null fields on the receiving side), the literal constitutive-loss invariant for state crossing a process boundary.
- In computing, state serialization across a process or network boundary cannot transmit closures, open descriptors, or runtime-only objects, and microservice migrations regularly discover state that lived in the monolith and did not survive the split.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:16dec3542380 · see in the full table