Skip to content
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.

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

chore: add load-on-startup configuration for custom Vaadin servlet #1712

Merged
merged 3 commits into from
Sep 20, 2022

Conversation

mcollovati
Copy link
Contributor

As of Flow 23.2, Vite dev-server needs VaadinServlet to be initialized before to start. In order to have Vite starting eagerly (before any HTTP request), VaadinServlet must be registered with load-on-startup attribute to a value greater than zero. For custom VaadinServlet this must be done explicitly by the developer.
This change updates example code defining custom Vaadin Servlet by adding load-on-startup setting.

Part of vaadin/flow#14479

As of Flow 23.2, Vite dev-server needs VaadinServlet to be initialized before
to start. In order to have Vite starting eagerly (before any HTTP request),
VaadinServlet must be registered with load-on-startup attribute to a value
greater than zero. For custom VaadinServlet this must be done explicitly by
the developer.
This change updates example code defining custom Vaadin Servlet by adding
load-on-startup setting.

Part of vaadin/flow#14479
@github-actions github-actions bot added the Language unchecked English language and AsciiDoc formatting checks haven't been done label Sep 13, 2022
@aws-amplify-eu-west-1
Copy link

This pull request is automatically being deployed by Amplify Hosting (learn more).

Access this pull request here: https://pr-1712.dcmp4ajsd49kq.amplifyapp.com

@jouni jouni removed the Language unchecked English language and AsciiDoc formatting checks haven't been done label Sep 13, 2022
@mshabarov mshabarov merged commit 64bf26f into latest Sep 20, 2022
@mshabarov mshabarov deleted the chore/custom_servlet_load_on_startup branch September 20, 2022 08:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants