Hi Hantsy,
In general you could write an extension that modifies the AnnotatedType to remove the annotation that declares the interceptor binding. @all We should think about supporting @BypassInterceptors in Deltaspike, wdyt? Not that I like this "feature" of Seam 2 that much (imho it works around some design flaws of Seam 2), but it would make a migration from Seam 2 to Deltaspike much easier. Cheers, Arne Am 29.12.12 03:29 schrieb "hantsy" unter <[email protected]>: >Thanks, gerhard. Is there a way to disable interceptors globally or >bypass some interceptors on certain managed beans? > >Hantsy > >On 12/28/2012 10:39, Gerhard Petracek wrote: >> hi hantsy, >> >> in deltaspike (and codi) we are using interceptor-strategies which >>allow to >> provide alternative (/specialized) interceptor-implementations (see >> org.apache.deltaspike.core.spi.InterceptorStrategy as well as the usage >>of >> it). >> >> regards, >> gerhard >> >> >> >> 2012/12/28 hantsy <[email protected]> >> >>> Hi all, >>> >>> I know there are some way to use alternative Managed Bean at runtime in >>> CDI. but how to process Interceptor. >>> >>> 1. I want to use custom Interceptor(esp extended from the Interceptor >>> and provides some different behavior) instead of the one shipped by >>>some >>> framework/tools at runtime ? >>> >>> 2. How to disable an interceptor at runtime for one ManagedBean(like >>> Seam 2 bypass annotation), and disable it globally? >>> >>> >>> Hantsy >>> >
