That's expected. The non-cdi interceptors are expected to be partially
managed by the EE container (resource injection). If you need resource
injection in the non-CDI interceptors you can use InjectionTargetBuilder
to customize this behavior, e.g:
On 06/02/2015 06:15 PM, Emily Jiang wrote:
For managed beans (@ManagedBean classes), they are java EE component
classes. They support both cdi and non-cdi interceptors. When I create
a instance using injectionTarget.produce(), I got hold of the instance
with both cdi and non-cdi interceptors associated. However, the
@Resource injection point on the non-cdi interceptors are not injected
when Weld creates the interceptor instances.
Is there anything I have missed or this is a bug?
weld-dev mailing list