|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectorg.apache.myfaces.extensions.cdi.core.api.provider.BeanManagerProvider
public class BeanManagerProvider
This class provides access to the BeanManager by registring the current BeanManager in an extension and making it available via a singleton factory
This is really handy if you like to access CDI functionality from places where no injection is available.
Usage:
BeanManager bm = BeanManagerProvider.getInstance().getBeanManager();
Constructor Summary | |
---|---|
BeanManagerProvider()
|
Method Summary | |
---|---|
javax.enterprise.inject.spi.BeanManager |
getBeanManager()
|
static BeanManagerProvider |
getInstance()
Singleton accessor |
static boolean |
isActive()
|
void |
setBeanManager(javax.enterprise.inject.spi.AfterBeanDiscovery abd,
javax.enterprise.inject.spi.BeanManager beanManager)
It basiscally doesn't matter which of the system events we use, but basically we |
Methods inherited from class java.lang.Object |
---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Constructor Detail |
---|
public BeanManagerProvider()
Method Detail |
---|
public static boolean isActive()
public static BeanManagerProvider getInstance()
public javax.enterprise.inject.spi.BeanManager getBeanManager()
BeanManager
public void setBeanManager(@Observes javax.enterprise.inject.spi.AfterBeanDiscovery abd, javax.enterprise.inject.spi.BeanManager beanManager)
abd
- event which we don't actually use ;)beanManager
- the BeanManager we store and make available.
|
||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |