Releases: vaadin/quarkus
Vaadin Quarkus add-on 2.0.0.rc1 pre-release
Pre-release for Vaadin 24 based on Jakarta EE 10.
Changes since 2.0.0.beta1
- Upgrade Quarkus version to 3.0.0.Alpha3 (#93)
Full Changelog: 2.0.0.beta1...2.0.0.rc1
Vaadin Quarkus add-on 2.0.0.beta1 pre-release
Pre-release for Vaadin 24 based on Jakarta EE 10.
Features
- Support for Jakarta EE 10 and Servlet 6.0.
Full Changelog: 1.1.3...2.0.0.beta1
Vaadin Quarkus add-on 2.0.0.alpha4 pre-release
Pre-release for Vaadin 24 based on Jakarta EE 9.
What's Changed
- test: fix missing lookup mock by @caalador in #91
- fix: updates after removal of deprecated Flow code by @MarcinVaadin in #92
Full Changelog: 2.0.0.alpha3...2.0.0.alpha4
Vaadin Quarkus add-on 2.0.0.alpha3 pre-release
Pre-release for Vaadin 24 based on Jakarta EE 9.
What's Changed
- fix: make sure annotated endpoints works along Vaadin PUSH by @mcollovati in #86
Full Changelog: 2.0.0.alpha2...2.0.0.alpha3
Vaadin Quarkus add-on 1.1.3
This version targets Vaadin 23.2, 23.1 and 22.
Changes since 1.1.2:
Fixes
Here is a list of all changes since 1.1.2
Vaadin Quarkus add-on 2.0.0.alpha2 pre-release
Pre-release for Vaadin 24 based on Jakarta EE 9.
Changes since 2.0.0.alpha1
:
- updated
Quarkus
dependency to3.0.0.Alpha1
Full Changelog: 2.0.0.alpha1...2.0.0.alpha2
Vaadin Quarkus add-on 2.0.0.alpha1 pre-release
Pre-release for Vaadin 24 based on Jakarta EE 9.
Build on top of Flow 24.0.0.alpha4
and Quarkus 3
snapshot (999-jakarta-SNAPSHOT).
Please note that Quarkus 3 is using internally Jakarta EE 10 with Servlet 6 which are backwards compatible with Jakarta EE 9 and Servlet 5 used by Flow 24.
Requires JDK 17.
Full Changelog: 1.1.2...2.0.0.alpha1
Vaadin Quarkus add-on 1.1.2
This version targets Vaadin 23.2, 23.1 and 22.
Changes since 1.1.1:
Fixes:
-
Set load-on-startup for automatically registered Vaadin servlets (#84) | Issue
When using Vite, DevModeInitializer blocks dev-server startup until a VaadinServlet is deployed because it needs to get the servlet path to use. If the container lazily loads servlets, Vite will not start until the first HTTP request for the Vaadin servlet is received. This change sets load-on-startup feature for all Vaadin Servlet registered by the extension, to ensure that Vite is loaded at the startup of the Web application. A warning message is shown for custom Vaadin servlets that do not set loadOnStartup on WebServlet annotation.
-
Add RouterLayout as bean classes (#85) | Issue
Currently RouterLayout implementations are ignored by CDI in Quarkus. This change specify RouterLayout implementors as additional bean classes to be analysed during bean discovery.
Here is a list of all changes since 1.1.1
Vaadin Quarkus add-on 1.1.1
This version targets Vaadin 23.1 on top of Flow 23.
Changes since 1.1.0:
Fixes:
- Skip user
VaadinServlet
s without@WebServlet
instead of throwing NPE (#77)
IfVaadinServlet
without@WebServlet
annotation present (like when vaadin-cdi happened to be in classpath) currently quarkusBuild will fail with NPE. This patch skips such servlets with a warning in log.
Here is a list of all changes since 1.1.0
Vaadin Quarkus add-on 1.1.0
This version targets Vaadin 23.1 on top of Flow 23.
Changes since 1.0.0:
-
Make Vaadin Push functionality work (#69)
Added a build step to initialise a customised Vert.x handler that attaches HTTP session from upgrade request to the WebSocket exchange so that VaadinPushHandler
can work. -
Fixes on user servlet registrations (#58)
@WebServlet.urlPatterns
are read as string array from annotation.@WebServlet.value
is also taken into account for mappings. Added check to prevent NPE when reading init parameters. Use@WebServlet.name
as servlet name, if present.
Here is a list of all changes since 1.0.0