Many, many thanks, I would have been lost without you! You saved me at least one week
reading (and trying to understand) the JBoss AOP source code.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841007#3841007
Reply to the post :
http://www.jboss.org/index.h
Ops!
| public class StackHeightAspect implements IStackHeight
| {
| private int height;
|
| public int size ()
| {
|return height;
| }
|
| public Object pushInvocation ( MethodInvocation invocation ) throws Throwable
| {
| ++ t
I took a look at your example:
1) Initially when I ran it the class cast failed. However, I found this to be due to
running within Eclipse, with your jboss-aop-stack on the source path. And my personal
build.xml is set up to use the Eclipse output classes. For some reason, this was
causing Stac
Mixins are definitely a good start, but nevertheless it's very hard, because I have to
split the aspect into the static (mixin) and the dynamic part (interception). My
feelings about this are that this is not in the spirit of AOP.
But let's get to the facts. As far as I understand the WIKI aspec
I'm not familiar with AspectJ, but I think the examples you show (if I have understood
them correctly) should be possible with JBossAOP. I'm just thinking loud, but with a
combination of mixin classes and per instance aspects I reckon you could acheive what
you're after. They are documented on t
