[
https://issues.apache.org/jira/browse/OWB-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125267#comment-15125267
]
Mark Struberg commented on OWB-1107:
------------------------------------
I introduced a bean-discovery-mode='scoped'.
In that mode all classes like with bean-discovery-mode 'all' (or CDI-1.0 empty
beans.xml) will get picked up as AnnotatedTypes and the ProcessAnnotatedType
will get fired.
But only the following AnnotatedTypes will later end up as Bean<T> if they:
* either have an explicit CDI scope annotation
* are an Interceptor or a Decorator
* are a JavaEE bean
* or have a StereoType
if the scanned and processed AnnotatedType is just a plain Java Class it will
NOT get picked up as @Dependent scoped bean automatically anymore.
> Scanning mode: Like Annotated but send PAT allowing Extensions to add beans
> ---------------------------------------------------------------------------
>
> Key: OWB-1107
> URL: https://issues.apache.org/jira/browse/OWB-1107
> Project: OpenWebBeans
> Issue Type: Improvement
> Reporter: Karl Kildén
> Assignee: Mark Struberg
>
> The annotated Scanning mode does not send ProcessAnnotatedType unless the
> bean has a scope. The important thing missing is a better way for CDI
> extensions to be able to add beans manually even though they are not
> annotated by dynamically assigning a scope.
> Thus this mode would send ProcessAnnotatedType for all beans but only
> process/store Beans which have an explicit scope after that.
> One use case is for example old JSF Beans annotated beans with faces scopes
> that getautomatically turned into their CDI equals by Deltaspike
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
