recedence ?
>
> http://eclipse.org/aspectj/doc/next/adk15notebook/ataspectj-declare.html
>
> cheers,
> Andy
>
> On 14 July 2010 15:49, Stephen Boesch wrote:
> > Does annotation based @AspectJ support precedence?
> > If I have
> > @Aspect
> &g
Does annotation based @AspectJ support precedence?
If I have
@Aspect
public class LowerPriorityAspect {
..
}
@Aspect
public class HigherPriorityAspect {
..
}
Then
public class SomeAdvisedClass {
public void someMethodAdvisedByBothAspects() {
}
}
So, how would I perform the equivalent of
but to get better assistance on the mailing list
> if you post complete programs you will likely get a faster response.
>
> My advice would be to build up your pointcuts from tiny pieces that do
> exactly what you are expecting. Did you attach advice to
> notInMethods() - does it mat
nMethods() {
>> }
>>
>> @Around(value = "!notInMethods() && execution(public * *.get* (..)) &&
>> this(dao)", argNames = "thisJoinPoint, dao")
>>
>>
>> 2010/7/13 Stephen Boesch
>>
>> The development process for asp
ling can tell me why nothing gets advised
anymore?
@Pointcut(value = "execution(public * *.getManagedClass())")
public void notInMethods() {
}
@Around(value = "!notInMethods() && execution(public * *.get* (..)) &&
this(dao)", argNames = "thisJoinPoint, dao
The development process for aspectj is proving to be very cumbersome / slow
for a non-adept. I'd like clear understanding of the selection process of
pointcut's, to know what's going on and why my pointcut expressions are not
performing as expected.
What are options for tooling?
Also, should I
!within(ASPECT-NAME) excludes call to the method as well as
> execution.
>
> -Ramnivas
>
>
> On Tue, Jul 13, 2010 at 6:22 PM, Stephen Boesch wrote:
>
>> What you show below is happening, but should have been avoided by the
>> !within(*ApplyStatisticsDaoAllPublicMethod
I'm using the AspectJ weaver (in Intellij) -- so I *think *that means it
should be supported .. ?
2010/7/13 Ramnivas Laddad
> Are you using Spring AOP (i.e. proxy-based AOP) or AspectJ (i.e. byte-code
> weaving based AOP)?
>
> -Ramnivas
>
> On Tue, Jul 13, 2010 at 5:20 PM
ublic * *(..)) && *
!within(ApplyStatisticsDaoAllPublicMethodsAspect)* && this(dao)",
argNames="thisJoinPoint, dao")
But it does have the recursion.
2010/7/13 Stephen Boesch
> Funny I had seen examples using !within(). So I coded
> !within(ApplyStatisicsDaoAllP
oinPoint, WaterfallORMDao dao)
throws Throwable {
...
I imagine it's a v common thing to want to instrument all public
non-constructor methods. Help pls ;)
2010/7/13 Stephen Boesch
> Pls correct my "humble" (read: "incorrect"..) attempt at having the
> po
Pls correct my "humble" (read: "incorrect"..) attempt at having the
pointcut avoid all constructors:
@Around(value = "*!initialization(new(..))* && < other conditions ..>
___
aspectj-users mailing list
aspectj-users@eclipse.org
https://dev.eclipse.org/
ao (and its execution is not within the
> aspect)... go to 1
>
> -Ramnivas
>
> On Tue, Jul 13, 2010 at 1:40 PM, Stephen Boesch wrote:
>
>> In the following aspect, the bolded methods cause infinite recursion due
>> to re-invocation of the pointcut. I don't ge
In the following aspect, the bolded methods cause infinite recursion due to
re-invocation of the pointcut. I don't get it: the pointcut conditions
include
* !within(ApplyStatisticsDaoAllPublicMethodsAspect) *
So why did that not avoid the recursion?
@Aspect
public class ApplyStatisticsDaoAllP
13 matches
Mail list logo
