Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify managed bean definition to exclude BeanCompatibleExtension impls #663

Closed
manovotn opened this issue Apr 21, 2023 · 0 comments · Fixed by #664
Closed

Clarify managed bean definition to exclude BeanCompatibleExtension impls #663

manovotn opened this issue Apr 21, 2023 · 0 comments · Fixed by #664
Assignees
@manovotn
Milestone
CDI 4.1

Comments

@manovotn
Copy link
Contributor

Currently, the specification states that a class implementing Extension isn't a managed bean:

A Java class is a managed bean if it meets all of the following conditions:

  • It does not implement jakarta.enterprise.inject.spi.Extension.

However, it fails to mention BuildCompatibleExtension.
Note that BCE are already forbidden from becoming bean by javadoc on BCE class - see this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@manovotn manovotn

Labels
None yet
Projects
None yet
Milestone
CDI 4.1
Development

Successfully merging a pull request may close this issue.

Explicitly state that classes implementing BuildCompatibleExtension i… manovotn/cdi
1 participant
@manovotn