[cdi-dev] Back on bean defining annotations

Jozef Hartinger jharting at redhat.com
Thu Mar 20 11:06:15 EDT 2014


Agreed but this approach of splitting things too much seems overly 
complicated to me. Let's not tie the bean defining annotation definition 
to the @Scope/@NormalScope meta-annotation presence. Let's instead say 
that all normal scopes are bean defining annotations. It will then be 
implicit that an annotation is a bean defining if either it is annotated 
with @NormalScoped or is added as 
BeforeBeanDiscovery.addScope(MyFirstScope.class,true,<true | false>)

Jozef

On 03/19/2014 04:30 PM, Antoine Sabot-Durand wrote:
> Hi all,
>
> Im' back with the main subject of this MR.
>
> To resolve CDI-377 we decided to exclude from the « Bean defining annotations » set, all Pseudo Scope type (scope annotation having the meta annotation @Scope) except @Dependent.
> So all normal scope annotation (built-in and user defined) are Bean Defining Annotation.
>
> Now what about a normal scope added with :
>
> 1) BeforeBeanDiscovery.addScope(MyFirstScope.class,true,<true | false>) ?
>
> And a pseudo scope added with :
>
> 2) BeforeBeanDiscovery.addScope(MySecondScope.class,false,<true | false>) ?
>
>
> For me MyFirstScope (defined in 1) should be a bean defining annotation while MySecondScope shouldn't.
>
> Any thought ?
>
> Antoine
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140320/aeee2ef1/attachment-0001.html 


More information about the cdi-dev mailing list