From ca64fc236070506570c23731def195462e27d6e8 Mon Sep 17 00:00:00 2001 From: Jouni Koivuviita Date: Thu, 11 Jul 2024 12:45:26 +0300 Subject: [PATCH] language fix --- articles/upgrading/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/upgrading/index.adoc b/articles/upgrading/index.adoc index 0d4c754198..c2753ee6ad 100644 --- a/articles/upgrading/index.adoc +++ b/articles/upgrading/index.adoc @@ -280,7 +280,7 @@ Before migrating, find the corresponding version of the Jakarta EE 10-compatible CDI 4.0 specification -- which is part of Jakarta EE 10 -- changes the default value of the `bean-discovery-mode` attribute to `annotated` and uses `annotated` as the default when an empty [filename]`beans.xml` file is found in a deployment. See https://jakarta.ee/specifications/cdi/4.0/[Jakarta CDI page] for more information. -To let the container scan and manage Vaadin components and views when the `bean-discovery-mode` attribute is not defined and the default is used, you should annotate Vaadin components and views with the `com.vaadin.cdi.annotation.CdiComponent` to allow Vaadin them to be detected correctly as CDI beans. +To let the container scan and manage Vaadin components and views when the `bean-discovery-mode` attribute is not defined and the default is used, you should annotate Vaadin components and views with the `com.vaadin.cdi.annotation.CdiComponent` to allow them to be detected correctly as CDI beans. As an alternative, you can set `bean-discovery-mode=all` in the [filename]`beans.xml` file if it's applicable to your project. However, this isn't recommended.