deltaspike-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Struberg <strub...@yahoo.de>
Subject Re: How to replace and disable Interceptor at runtime.
Date Sat, 29 Dec 2012 06:32:20 GMT
Either by providing an empty InterceptorStrategy or by dynamically removing the interceptor
annotation from the beans via a CDI exension.

Or just remove them from the beans.xml.

LieGrue,
strub




----- Original Message -----
> From: hantsy <hantsy@yahoo.com.cn>
> To: deltaspike-dev@incubator.apache.org
> Cc: 
> Sent: Saturday, December 29, 2012 3:29 AM
> Subject: Re: How to replace and disable Interceptor at runtime.
> 
>T hanks, 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 <hantsy@yahoo.com.cn>
>> 
>>>  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
>>> 
> 

Mime
View raw message