Mailing-List: contact deltaspike-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltaspike-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gerhard.petracek@gmail.com
 designates 209.85.220.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAF9TksOY8epr1+ZmhU9mwAne_GOtjQoZqPdrYdZhj_8B0k92AA@mail.gmail.com>
References: <50DE556C.1090800@yahoo.com.cn>
 <97621E8BA4D496449BC4D1AB06E0FB70057695@K99F-PEXC01.openknowledge.de>
 <CAF9TksOY8epr1+ZmhU9mwAne_GOtjQoZqPdrYdZhj_8B0k92AA@mail.gmail.com>
From: Gerhard Petracek <gerhard.petracek@gmail.com>
Date: Sat, 29 Dec 2012 19:46:06 +0100
Message-ID: 
 <CAGJtJfGSiyBJR691qsHLbB+MLJ3bBNsNFU6ECaGV2Jn+F1S6XQ@mail.gmail.com>
Subject: Re: How to replace and disable Interceptor at runtime.
To: deltaspike-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec54ee81288d55d04d20232ae

--bcaec54ee81288d55d04d20232ae
Content-Type: text/plain; charset=ISO-8859-1

i agree with jason (and that's also what we have done so far).

regards,
gerhard


2012/12/29 Jason Porter <lightguard.jp@gmail.com>

> Arne: I'm not quite sure I see the point in doing this. Interceptors in
> Seam2 were completely different than in CDI. If you don't want an
> interceptor, remove the annotation, or take it out of the beans.xml.
>
> I also don't see a use case for @BypassInterceptors. If there's a use case
> for it, then we can consider it, but I don't want to start adding things to
> DeltaSpike without clearly defined use cases.
>
>
> On Sat, Dec 29, 2012 at 3:13 AM, Arne Limburg <
> arne.limburg@openknowledge.de
> > wrote:
>
> > 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 <hantsy@yahoo.com.cn>:
> >
> > >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 <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
> > >>>
> > >
> >
> >
>
>
> --
> Jason Porter
> http://lightguard-jp.blogspot.com
> http://twitter.com/lightguardjp
>
> Software Engineer
> Open Source Advocate
>
> PGP key id: 926CCFF5
> PGP key available at: keyserver.net, pgp.mit.edu
>

--bcaec54ee81288d55d04d20232ae--