Skip to content

Add note about Vaadin scoped beans and serialization #4244

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TatuLund merged 3 commits into from
May 22, 2025
Merged

Add note about Vaadin scoped beans and serialization #4244

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a78afd0
Add note about Vaadin scoped beans and serialization
TatuLund Apr 9, 2025
e0256bf
Update articles/flow/integrations/cdi/contexts.adoc
TatuLund Apr 9, 2025
bf49baf
Merge branch 'latest' into cdi-bean-serialization-note
TatuLund May 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions articles/flow/integrations/cdi/contexts.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -281,4 +281,8 @@ Injected beans aren't preserved when they're `UIScoped`, but only when they're `
The `UI` instance itself isn't preserved, but routing components are preserved. Any bean tied to the `UI` instance with `UIScoped` is recreated. The preserved routing components are moved to the new `UI`. To preserve beans during a browser refresh, you need to use `@RouteScoped`, as shown earlier.


.Vaadin scoped bean need to be serializable
[NOTE]
Scoped bean instances are stored in the session. This means in case you persist sessions using some 3rd party tool, the beans needs to be serializable.

[discussion-id]`4AAFA7A1-CF85-42D6-A7F2-E0CB0DB70FD1`
Loading