You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Prasad Kashyap <go...@gmail.com> on 2007/05/01 17:44:53 UTC
Re: Problems excluding default interceptor
Refreshing the problem again -
This problem exists uniformly for both annotation and xml specification.
If you try to exclude a class from default interceptors, the lifecycle
events are excluded but some of the business methods are not.
Those business methods that have a @ExcludeClass specified on it, get
ignored by the @ExcludeDefault specified at the class level (either by
annotation or xml)
When a @ExcludeDefault is specified at the class level, default
interceptors are excluded for the business methods only if they do not
have a @ExcludeClass specified on them.
Cheers
Prasad
On 3/29/07, Prasad Kashyap <go...@gmail.com> wrote:
> On 3/29/07, Prasad Kashyap <go...@gmail.com> wrote:
> > I had made an error of using, in my DD, the bean's class name instead
> > of the overriden bean name. Thanks to David for asking that very basic
> > question. Sorry if I wasted anybody's time on this.
> >
> > Problem 1 below is not there.
> >
> > Problem 2 exists uniformly for both annotation and xml specification.
> > Here is the problem.
> > If you try to exclude a class from default interceptors, the lifecycle
> > events are excluded but the business methods are not.
>
> Some more information - when a @ExcludeDefault is specified at the
> class level, default interceptors are excluded for the business
> methods only if they do not have a @ExcludeClass specified on them.
>
> If a method has a @ExcludeClass specified on it, it ignores the
> @ExcludeDefault specified at the class level
>
> Cheers
> Prasad
>
> >
> > Cheers
> > Prasad
> >
> > On 3/27/07, Prasad Kashyap <go...@gmail.com> wrote:
> > > I have an ejb-jar with 3 beans and a default interceptor with wildcard
> > > "*" that applies to all beans.
> > >
> > > Problem 1:
> > > ---------------
> > >
> > > In FirstBean, I specify an @ExcludeDefault for a method. This sticks.
> > > In SecondBean, I specify an <exclude-default-interceptor> for one
> > > method of the bean. It is ignored.
> > > In ThirdBean, I specify an <exclude-default-interceptor> for the whole
> > > class. It is ignored.
> > >
> > >
> > > Problem 2:
> > > ---------------
> > > I now specify an @ExcludeDefaultInterceptor at the class level. Only
> > > the lifecycle events are excluded. The methods calls are still
> > > intercepted.
> > >
> > >
> > > Cheers
> > > Prasad
> > >
> >
>
Re: Problems excluding default interceptor
Posted by Prasad Kashyap <go...@gmail.com>.
https://issues.apache.org/jira/browse/OPENEJB-583
Cheers
Prasad
On 5/1/07, Prasad Kashyap <go...@gmail.com> wrote:
> Refreshing the problem again -
>
> This problem exists uniformly for both annotation and xml specification.
>
> If you try to exclude a class from default interceptors, the lifecycle
> events are excluded but some of the business methods are not.
>
> Those business methods that have a @ExcludeClass specified on it, get
> ignored by the @ExcludeDefault specified at the class level (either by
> annotation or xml)
>
> When a @ExcludeDefault is specified at the class level, default
> interceptors are excluded for the business methods only if they do not
> have a @ExcludeClass specified on them.
>
> Cheers
> Prasad
>
>
> On 3/29/07, Prasad Kashyap <go...@gmail.com> wrote:
> > On 3/29/07, Prasad Kashyap <go...@gmail.com> wrote:
> > > I had made an error of using, in my DD, the bean's class name instead
> > > of the overriden bean name. Thanks to David for asking that very basic
> > > question. Sorry if I wasted anybody's time on this.
> > >
> > > Problem 1 below is not there.
> > >
> > > Problem 2 exists uniformly for both annotation and xml specification.
> > > Here is the problem.
> > > If you try to exclude a class from default interceptors, the lifecycle
> > > events are excluded but the business methods are not.
> >
> > Some more information - when a @ExcludeDefault is specified at the
> > class level, default interceptors are excluded for the business
> > methods only if they do not have a @ExcludeClass specified on them.
> >
> > If a method has a @ExcludeClass specified on it, it ignores the
> > @ExcludeDefault specified at the class level
> >
> > Cheers
> > Prasad
> >
> > >
> > > Cheers
> > > Prasad
> > >
> > > On 3/27/07, Prasad Kashyap <go...@gmail.com> wrote:
> > > > I have an ejb-jar with 3 beans and a default interceptor with wildcard
> > > > "*" that applies to all beans.
> > > >
> > > > Problem 1:
> > > > ---------------
> > > >
> > > > In FirstBean, I specify an @ExcludeDefault for a method. This sticks.
> > > > In SecondBean, I specify an <exclude-default-interceptor> for one
> > > > method of the bean. It is ignored.
> > > > In ThirdBean, I specify an <exclude-default-interceptor> for the whole
> > > > class. It is ignored.
> > > >
> > > >
> > > > Problem 2:
> > > > ---------------
> > > > I now specify an @ExcludeDefaultInterceptor at the class level. Only
> > > > the lifecycle events are excluded. The methods calls are still
> > > > intercepted.
> > > >
> > > >
> > > > Cheers
> > > > Prasad
> > > >
> > >
> >
>