[webbeans-dev] which would be easier to implement?

[Pete Muir]

Implementation wise, I'm not sure it makes any difference, as you  
still need to know what bean specializes what. Further, you can cache  
the result of a resolve(), so there is no performance overhead at  
runtime.

Conceptually, I think it works better as is, and I think Mark makes a  
valid point.

Mark, any comment on impl for OWB?

On 25 Aug 2009, at 08:36, Mark Struberg wrote:

> What happens if you have a @SessionScoped bean in an EAR lib which  
> is @Specializes in 2 different WebApps within this EAR but not in a  
> 3rd one?
>
> Might get tricky if we drop the original bean, isn't?
>
> LieGrue,
> strub
>
> --- On Mon, 8/24/09, Gavin King <gavin.king at gmail.com> wrote:
>
>> From: Gavin King <gavin.king at gmail.com>
>> Subject: [webbeans-dev] which would be easier to implement?
>> To: "Pete Muir" <pmuir at redhat.com>, "WebBeans" <webbeans-dev at lists.jboss.org 
>> >
>> Date: Monday, August 24, 2009, 8:45 PM
>> Should we say that any bean that is
>> specialized by an enabled bean is
>> disabled - i.e. no Bean object exists? Or should we leave
>> it like it
>> is now?
>>
>> -- 
>> Gavin King
>> gavin.king at gmail.com
>> http://in.relation.to/Bloggers/Gavin
>> http://hibernate.org
>> http://seamframework.org
>> _______________________________________________
>> webbeans-dev mailing list
>> webbeans-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>>
>
>
>
> _______________________________________________
> webbeans-dev mailing list
> webbeans-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/webbeans-dev