Vaadin Flow 24.6.0.alpha3

Changes since 24.6.0.alpha2

All changes

New features

• Extend WebPushMessage with the custom settings
  Commit · Pull request · Issue

  Add an API to set custom options as described in https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerRegistration/showNotification#parameters

Fixes

• Support serialization of Vaadin scoped beans
  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
  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.

• Ignore CDI related classes when finding component location
  Commit · Pull request

• Theme asset collection and ComponentTracker path check
  Commit · Pull request

  in windows. Fix componentTracker patch check in windows.