Skip to content

Vaadin Flow 24.5.4
Compare
Choose a tag to compare
@vaadin-bot vaadin-bot released this 07 Nov 15:10
· 21 commits to 24.5 since this release
24.5.4
65547dc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Changes since 24.5.3

All changes

Fixes

  • Support serialization of Vaadin scoped beans (#20394)
    Commit · Pull request · Issue

    Makes sure that VaadinSession and UI thread locals are available during both serialization and deserialization, to allow other libraries to perform inspection and injection of Vaadin scoped beans. Also refactors VaadinRouteScope to be independent from VaadinService when fetching RouteScopeOwner annotation for the bean, and replaces VaadinSession.unlock() calls with direct access to the lock instance to prevent unwanted push during bean lookup. Part of vaadin/kubernetes-kit#140

  • Resume client to server communication after web socket reconnection (#20283)
    Commit · Pull request · Issue

    When a websocket PUSH connection is closed and re-established because of a network failure, the RequestResponseTracker.hasActiveRequest is not reset, prenvint the Flow client to send additional messages to the server. This change will reset the flag on reconnection. It also will track unsent PUSH message over websocket, to retry the delivery once the connection is re-established, preventing client resynchronization. In addition, it sets a default value of 12 for the Atmospehere maxWebsocketErrorRetries setting, to ensure that the Flow client will attempt to reconnect with web socket transport several times, instead of immediately downgrade to long-polling after first failed connection.

  • Theme asset collection and ComponentTracker path check (#20390)
    Commit · Pull request

    in windows. Fix componentTracker patch check in windows.

  • Ignore CDI related classes when finding component location (#20405)
    Commit · Pull request

Assets 2
Loading