Community
Participate
Working Groups
See forums posts from Jean-Louis Pasturel. From playing around with test programs derivative of what he posted I have seen two serious problems. An NPE crash in the around advice (which can be worked by using -XnoInline) and an illegal access error when the advised location is unable to call the proceed advice in the aspect because it cannot see the method in the other package. I will put the testcases into CVS for this first.
All fixed and tests added. The problem was that the superaspect was in code style and the subaspect was in annotation style. Declaring a concrete aspect in XML causes us to generate an annotation style subaspect. Around advice inlining is done differently depending on whether the advice is declared in a codestyle aspect or an annotation style aspect. Unfortunately we were making the decision about what to do based on the concrete aspect type that was leading to the advice being applied, rather than which type declared the advice. I have switched the decision to be based on which type declares the advice. fix will be in a dev build shortly
Will this fix support annotation-style aspects that extend abstract code-style aspects in general? Glassbox uses code-style aspects to work with Java 1.4 but many Java 5+ users would like to extend them with annotation-style aspects...
I see no reason why that should not work Ron - have you been having trouble with it??
Yes I did in past. I'll try with the latest build and see if it works as expected.
