Details
-
Type:
Enhancement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 1.1.3.Final
-
Fix Version/s: 1.1.4.Final
-
Component/s: Proxies
-
Labels:None
Description
In Validator it does:
if (beanManager.getServices().get(MetaAnnotationStore.class).getScopeModel(resolvedBean.getScope()).isNormal() && !Proxies.isTypeProxyable(ij.getType())) {
|
throw new UnproxyableResolutionException(INJECTION_POINT_HAS_NON_PROXYABLE_DEPENDENCIES, ij);
|
}
|
which calls on Proxies:
public static boolean isTypeProxyable(Type type) {
|
return getUnproxyableTypeException(type) == null;
|
}
|
so the exception created by getUnproxyableTypeException() is eaten.
And that's exactly the exception that clearly explains why it's not proxyable, so that should be chained.
Gliffy Diagrams
Activity
- All
- Comments
- Work Log
- History
- Activity
- Links Hierarchy