Details
-
Type:
Sub-task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 0.1-incubating
-
Component/s: Core
-
Labels:None
Description
public <T> T getContextualReference(Class<T> type, boolean optionalBeanAllowed, Annotation... qualifiers)
public <T> T getContextualReference(String name, boolean optionalBeanAllowed, Class<T> targetType)
public <T> List<T> getContextualReferences(Class<T> type, boolean optionalBeanAllowed, Annotation... qualifiers)
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
if you provide a name, type,... and there is no cdi bean for it the behaviour is different.
optionalBeanAllowed == false && cdiBeanFound == false -> throw an exception
optionalBeanAllowed == true && cdiBeanFound == false -> return null
the alternative would be to return null and every caller has to do the exception part (if a cdi bean isn't optional) -> we will see different exceptions for the same reason.
Okay, got it, thanks.
CdiUtils sounds a bit too loose. I'd rather name it ContextualInstanceProvider and let it resolve the BeanManager internally.
resolved as part of the work for DELTASPIKE-17
#getContextualReferences is missing
What's the optionalBeanAllowed param drive?