Skip to content

Vaadin CDI Add-on 15.0.0.beta1 for Vaadin 24

Pre-release
Pre-release

Choose a tag to compare

View all tags
@mshabarov mshabarov released this 06 Feb 11:13
15.0.0.beta1
027314e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

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.

Assets 2
Loading