As Gonzalo said, you would firstly need to specify the common interface of the bean if you want to declare it as a class field and use different implementations of it.
Moreover, I think you could achieve it more elegant using the CDI's @Produces method; i.e. somewhat between these lines:
@Singleton
@Startup
public class Configuration {
private boolean someCondition;
@PostConstruct
private void init() {
someCondition = ... // get a value from DB, JMS, XML, etc.
}
@EJB(lookup="java:comp/env/myParticularBean")
MyBean myBean1;
@EJB(beanName="anotherTypeOfBeanInjectedByName")
MyBean myBean2;
@Produces
public MyBean produceMyBean() {
if (someCondition)
return myBean1;
} else {
return myBean2;
}
}
}
Then in your code you can just use:
@Inject
MyBean myBean;
and appropriate bean based on your condition will be injected for you.
If you don't need a field on class level you could use the old-way and locate the EJB in JNDI - in this way you have the control over what type and what bean should be located and used.
EDIT: I've added the @EJB
annotated beans to show where the 'myBean1' and 'myBean2' instances might come from.
This example shows that you can have one, single place where you define all your dependencies on different EJB implementations and other components. In an examle, this could be realised as a singleton EJB with @EJB fields, @PersistenceContext fields, etc.
Instead of doing it in the presented way, you can change return myBean1
to something like return context.lookup("JNDI_NAMESPACE_COORDINATES")
where context
is an instance of InitialContext
.
Hope this makes it more clear.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…