If the code is woven twice by 2 different tools ( AspectJ and Javassist), I
think it is difficult to handle a priority.
With AspectJ, you can handle priorities between advices when many aspects
are woven with a pointcut ( pointcut call or execution for example).
Jean-Louis Pasturel
-Mess
You were right, it was a user error on my side. The aspect and the unittest
were fine but the ejb tested live on the server did not get weaved indeed.
Your hint helped a lot, I thought its a conceptual problem.
Thanks,
Kristof
--
This mail was sent by an Android.
On Sep 2, 2009 6:07 PM, "Andrew
Hi Andy,
raised https://bugs.eclipse.org/bugs/show_bug.cgi?id=288577 . Sorry for
not writing the bug earlier, but I found no mention on documentation nor
any example of an after() returning(Object o) : set(), so I didn't know
if it was a bug or something else.
Simone
Andy Clement wrote:
Doe
Thanks for reply. I copy TapestryFilger.java to my own folder and rename it
(e.g. MyTapestryFiler.java) to use it in the web.xml as customized filter.
It works fine. The pointcut interceptor() can capture the execution of
doFilter() method. However, it just won't work if switch back using
Tapestry
Does this do what you want?
interface A { }
interface B { void foo();}
class BImpl implements B { public void foo() {System.out.println("foo
running");}}
@Aspect
class X {
@DeclareMixin("C")
public static B createB() {
return new BImpl();
}
Always raise VerifyErrors as bugs. They are more common with
annotation style than code style because of the reduced amount of
checking we can perform at compile/weave time. And annotation style is
still much younger in terms of maturity than code style.
Andy
2009/8/31 Andrew Eisenberg :
> Hi the
Does seem a little inconsistent. Raise a bugzilla to track clarifying
why it is the right behaviour or fixing it.
Andy
2009/8/27 Simone Gianni :
> Hi all,
> I don't know if this is a bug, or if it's a known or wanted behavior, but
> using after() returning(Object o) on a set() pointcut does not
