Mark Struberg created CDI-420:
Summary: add a bean-discovery-mode 'detected'
Project: CDI Specification Issues
Issue Type: Bug
Components: Packaging and Deployment
Affects Versions: TBD
Reporter: Mark Struberg
This is for some future CDI release.
We currently only have 3 bean-discovery-modes
The spec also currently says that ProcessAnnotatedType will only get fired (12.4) for
• each Java class, interface or enum deployed in an explicit bean archive, and
• each Java class with a bean defining annotation in an implicit bean archive.
• each session bean
Which means that we do not get the ProcessAnnotatedType event for any class in an
'annotated' or 'implicit' BDA which does _not_ have a bean defining
It might be useful to fire the ProcessAnnotatedType for all classes, but do not pick them
up as Beans if the (after PAT) do not have a valid scope. Effectively doing the processing
but not make them @Dependent automatically if there is no scope annotation at the end of
I'm not yet 100% sure how important this distinction is in practice. Just writing this
up to not forget about the idea...
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira