[webbeans-dev] Specialized beans

[Pete Muir]

Maybe I misunderstood, but we still have this para:

> When a selected alternative, as defined in Section 5.2, “Alternative  
> selection”, specializes a second bean, we can be certain that the  
> second bean is never instantiated or called by the container. Even  
> if the second bean defines a producer or observer method, the method  
> will be called upon an instance of the first bean.

Surely this, should say,

>  Even if the second bean defines a producer or observer method, the  
> method will not be called.


On 27 Aug 2009, at 00:49, Gavin King wrote:

> I've been discussing the following change with Pete:
>
> Currently, the spec says that when a bean X is specialized by some
> enabled bean Y, X is still considered enabled, and its producer
> methods are also enabled, but they get called on Y instead of X.
>
> However, the following is simpler to implement, specify, and probably
> understand:
>
>   When a bean X is specialized by an enabled bean Y, X and all its
> producer methods are considered disabled.
>
> This definition lets us get rid of the whole notion of "most
> specialized enabled bean".
>
> I'm attaching a spec which incorporates the necessary changes, mainly
> in 4.3 and 5.2.
>
> WDYT?
>
> -- 
> Gavin King
> gavin.king at gmail.com
> http://in.relation.to/Bloggers/Gavin
> http://hibernate.org
> http://seamframework.org
> <JSR-299-20090826.pdf>_______________________________________________
> webbeans-dev mailing list
> webbeans-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev