Skip to content

Commit

Permalink
Specify behavior for sealed types
Browse files Browse the repository at this point in the history
Sealed types are valid bean types, but they are unproxyable.

This commit only makes explicit what already implicitly follows from
the existing CDI specification and updates in the Java / JVM specifications.
  • Loading branch information
Ladicek committed Oct 13, 2023
1 parent 264a1a3 commit bf4dbf1
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
2 changes: 1 addition & 1 deletion spec/src/main/asciidoc/core/definition.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ The bean types of a bean are used by the rules of typesafe resolution defined in

Almost any Java type may be a bean type of a bean:

* A bean type may be an interface, a concrete class or an abstract class, and may be declared final or have final methods.
* A bean type may be an interface, a concrete class or an abstract class, may be declared sealed or non-sealed or final, and may have final methods.
* A bean type may be a parameterized type with actual type parameters and type variables.
* A bean type may be an array type.
Two array types are considered identical only if the element type is identical.
Expand Down
1 change: 1 addition & 0 deletions spec/src/main/asciidoc/core/implementation.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -662,6 +662,7 @@ Certain legal bean types cannot be proxied by the container:
* classes which don't have a non-private constructor with no parameters,
* classes which are declared final,
* classes which have non-static, final methods with public, protected or default visibility,
* sealed classes and sealed interfaces,
* primitive types,
* and array types.

Expand Down

0 comments on commit bf4dbf1

Please sign in to comment.