ClassNotFoundException for transient classes during Vaadin UI restoration
0 reputation · 26 Mar 2024, 21:59 UTC
The goal is to define a reliable verification approach for recovered UI state after backup restoration in a Vaadin Flow application that uses custom components and Spring-managed entities.
UI serialization persists the component tree as JSON. Custom components must handle transient fields to avoid data loss during restoration. Backend data restoration depends on matching entity schemas, and version mismatches in the serialization format can cause verification failures. Verification of recovered data assumes the underlying database remains intact and does not cover external migrations.
An unresolved design decision concerns client-side SessionStorage persistence of UI state across server restarts and its interaction with session expiry policies.
Should client-side SessionStorage be considered a valid persistence mechanism for UI state across server restarts? What criteria determine component identifier equivalence between a saved snapshot and a restored UI session? How should restoration be defined when the Vaadin minor version has changed the JSON serialization format?
vaadin