All bean modification mechanisms should still be available. A usecase for this
SPI is e.g. configuration via XML. This way you could add a bean without even
being in a BDA. Otoh if it's defined in a BDA it will get picked up as
@Dependent automatically (and I really hate this behaviour defined in the
spec...) So you first would need to drop the @Dependent bean and add a new one.
LieGrue,
strub
- Original Message
From: Eric Covener cove...@gmail.com
To: dev@openwebbeans.apache.org
Sent: Mon, August 9, 2010 3:14:14 PM
Subject: 299 q: AfterBeanDiscovery.addBean()
In 299, If a portable extension used AfterBeanDiscovery.addBean() to
add a managed bean to an application:
1) If that bean was already in a BDA we knew about, why bother adding
it this way?
2) If that bean was not already in a BDA, is it now uninterceptable
and undecoratable because there's no ways to enable anything for it?
I couldn't find an alternative mechanism for enablement.
--
Eric Covener
cove...@gmail.com
