Interceptors in generell should be supported but only via custom binding - not via "@Interceptors, @Intercepted and @Decorator"
2018-04-20 11:21 GMT+02:00 Luís Alves <[email protected]>: > So far I found that @Repository is actually a @PartialBeanBinding and I > found: "Currently CDI Interceptors applied via @Interceptors, @Intercepted > and @Decorator are not supported by our proxies! "...does it means that I'm > screwed ;)? > > LA > > On Fri, Apr 20, 2018 at 10:11 AM, Luís Alves <[email protected]> > wrote: > > > even with @ApplicationScoped the interceptor is not working :( can't > > figure out why...can't @Repository methods be intercepted? > > > > > > > > On Fri, Apr 20, 2018 at 9:53 AM, Luís Alves <[email protected]> > wrote: > > > >> since it's proxied...it should be OK...I guess it's like Spring's > >> repositories. > >> > >> On Fri, Apr 20, 2018 at 9:44 AM, Luís Alves <[email protected]> > >> wrote: > >> > >>> Hi, > >>> > >>> @Repository is @Dependent scoped...and seems that @Dependent don't run > >>> interceptors, so @CacheResult(cacheName = "my-cache") annotation isn't > >>> working :( > >>> I remember that some one proposed that @Repository could/should be > >>> @ApplicationScoped...if I change them do I have to worry with > anything? My > >>> EntityManager producer is the following: > >>> > >>> @Produces > >>> @RequestScoped > >>> public EntityManager get() > >>> { > >>> return entityManager; > >>> } > >>> > >>> I suppose I'll have a different EM for each HTTP request / MDB > >>> onMessage() / @Scheduled(cronExpression ="....")...am I correct? > >>> > >>> regards, > >>> LA > >>> > >> > >> > > >
