From e24bb0ea10da2c8d5ce788ad539537f6410d0623 Mon Sep 17 00:00:00 2001 From: Scott M Stark Date: Thu, 30 Nov 2023 11:20:28 -0600 Subject: [PATCH] + Updates for PR feedback Signed-off-by: Scott M Stark --- spec/src/main/asciidoc/core/implementation.asciidoc | 1 - spec/src/main/asciidoc/core/lifecycle.asciidoc | 4 ++-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/spec/src/main/asciidoc/core/implementation.asciidoc b/spec/src/main/asciidoc/core/implementation.asciidoc index d08efbff..c8495888 100644 --- a/spec/src/main/asciidoc/core/implementation.asciidoc +++ b/spec/src/main/asciidoc/core/implementation.asciidoc @@ -18,7 +18,6 @@ Portable extensions and build compatible extensions may provide other kinds of b A _managed bean_ is a bean that is implemented by a Java class. This class is called the _bean class_ of the managed bean. -The basic lifecycle and semantics of managed beans are defined by the CDI specification. If a managed bean has a non-static public field, its scope must be a <> (for example, `@Dependent` or `@Singleton`). If a managed bean with a non-static public field declares a normal scope, the container automatically detects the problem and treats it as a definition error. diff --git a/spec/src/main/asciidoc/core/lifecycle.asciidoc b/spec/src/main/asciidoc/core/lifecycle.asciidoc index 11e1bca0..eabd5dd9 100644 --- a/spec/src/main/asciidoc/core/lifecycle.asciidoc +++ b/spec/src/main/asciidoc/core/lifecycle.asciidoc @@ -109,9 +109,9 @@ The actual mechanics of bean creation and destruction varies according to what k ==== Lifecycle of managed beans -When the `create()` method of the `Bean` object that represents a managed bean is called, the container obtains an instance of the bean, as defined by this specification, calling the bean constructor as defined by <>, and performing dependency injection as defined in <>. +When the `create()` method of the `Bean` object that represents a managed bean is called, the container obtains an instance of the bean, calling the bean constructor as defined by <>, and performing dependency injection as defined in <>. -When the `destroy()` method is called, the container destroys the instance, as defined by this specification, and any dependent objects, as defined in <>. +When the `destroy()` method is called, the container destroys the instance, and any dependent objects, as defined in <>.