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(a)gmail.com> wrote:
From: Gavin King <gavin.king(a)gmail.com>
Subject: [webbeans-dev] which would be easier to implement?
To: "Pete Muir" <pmuir(a)redhat.com>, "WebBeans"
<webbeans-dev(a)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(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev