Not necessarily - i'm just saying I know there are some bugs we have in annotation style around advice, and they manifest as things like StackOverflow because the generated code is incorrect. These problems don't happen for code style around advice - because it can do more checking and do a better job of generating code.
you could try translating your pointcut/advice to code style and see if ajc likes it - or take a read of: https://bugs.eclipse.org/bugs/show_bug.cgi?id=126167 which describes some 'unwritten rules' about using @AJ Around advice. On 27/02/07, Santiago Aguiar <[EMAIL PROTECTED]> wrote:
Andy Clement wrote: With code style aspects we can do more type checking than we can for annotation style aspects - and there are some bugs related to specification of parameters for around advice, when using annotation style, that manifest as this kind of failure (StackOverflow) - when code style would work perfectly. This is why when I saw your failure, I assumed annotation style syntax. I'm using around advices. So the problem is that I probably have an ill defined pointcut?. Thanks! saludos, -- santiago aguiar netlabs Palmar 2548 Montevideo, Uruguay Tel. +(598 2) 707 7687 Fax. +(598 2) 709 4866 http://www.netlabs.com.uy _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
