CDI Integration for Vaadin
This is the Flow CDI integration final release for Vaadin 22.1.
Vaadin CDI add-on version 13.1.0 is now under commercial license and targets Vaadin 22.1 supported for Prime+ subscriptions.
All changes since version 13.0.0.
This is a pre-release of the Vaadin CDI add-on for Vaadin 22, built on top of Flow 9.1.0.alpha1.
Full Changelog: https://github.com/vaadin/cdi/compare/13.0.1...13.1.0.alpha1
This is a GA release of the Vaadin CDI add-on version 15.0.0 for Vaadin 24, built on top of Flow 24.0.0. Vaadin CDI add-on 15.0.0 is based on Jakarta EE 10 and requires Java 17+.
Breaking changes
CDI 4.0 specification changes the bean-discovery-mode attribute default to annotated and uses annotated as the default when an empty beans.xml is seen in a deployment, see https://jakarta.ee/specifications/cdi/4.0/.
To let the container scan and manage Vaadin components and views when the bean-discovery-mode attribute is not defined (default is used), one should annotate Vaadin components and views with the com.vaadin.cdi.annotation.CdiComponent annotation. Or set bean-discovery-mode=ALL if it's applicable to your project, but this is not a recommended way.
Features
Support for Jakarta EE 10: Servlet 6.0 and CDI 4.0 Adds a support for Jakarta EE 10 / Servlet 6.0 spec. Drops support for Servlet 3.
Retain RouteScoped parent layouts on route change When changing routes where a RouterLayout comes into play that has a RoutePrefix associated with it and where this routerlayout is annotated to be @RouteScoped the spec has changed between Vaadin CDI 12 and Vaadin CDI 13 so that strictly the RouteScopeOwner is considered to be the innermost Route component.
This change will result in RouterLayouts of this kind to have a RouteScopeOwner which will be themselves. This fits with the notion that the Route part which pertains to this RouterLayout does in fact not change.
Upgrade to SLF4j 2.0
Full Changelog: https://github.com/vaadin/cdi/compare/14.1.0...15.0.0
This is a pre-release of the Vaadin CDI add-on for Vaadin 24, built on top of Flow 24.0.0.rc1.
Based on Jakarta EE 10 / Servlet 6 and Java 17.
No user-facing changes since 15.0.0.beta1.
Full Changelog: https://github.com/vaadin/cdi/compare/15.0.0.beta1...15.0.0.rc1
This is a pre-release of the Vaadin CDI add-on for Vaadin 24, built on top of Flow 24.0.0.beta1. Requires Java 17+.
Breaking changes
CDI 4.0 specification changes the bean-discovery-mode attribute default to annotated and uses annotated as the default when an empty beans.xml is seen in a deployment, see https://jakarta.ee/specifications/cdi/4.0/.
To let the container scan and manage Vaadin components and views when the bean-discovery-mode attribute is not defined (default is used), one should annotate Vaadin components and views with the com.vaadin.cdi.annotation.CdiComponent annotation. Or set bean-discovery-mode=ALL if it's applicable to your project, but this is not a recommended way.
Features
Support for Jakarta EE 10: Servlet 6.0 and CDI 4.0 Adds a support for Jakarta EE 10 / Servlet 6.0 spec. Drops support for Servlet 3.
Retain RouteScoped parent layouts on route change When changing routes where a RouterLayout comes into play that has a RoutePrefix associated with it and where this routerlayout is annotated to be @RouteScoped the spec has changed between Vaadin CDI 12 and Vaadin CDI 13 so that strictly the RouteScopeOwner is considered to be the innermost Route component.
This change will result in RouterLayouts of this kind to have a RouteScopeOwner which will be themselves. This fits with the notion that the Route part which pertains to this RouterLayout does in fact not change.
Upgrade to SLF4j 2.0
No changes since 15.0.0.alpha4.
This is a pre-release of the Vaadin CDI add-on for Vaadin 24, built on top of Flow 24.0.0.alpha15.
Includes support for Jakarta EE 9 and Java 17.
Full Changelog: https://github.com/vaadin/cdi/compare/15.0.0.alpha3...15.0.0.alpha4