this problem is now fixed, it was a bug in javassist. the fix is atm only
available from the javassist cvs repository, but the upcoming jboss-aop 2.0
will include this fix.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977088#3977088
Reply to the post :
ht
hi, a simple workaround for the fieldproblem is to either to rename the field
variable so that it doesnt match the field of the subclass or make the field
variable private accessible. the only workaround for the overflow/loop problem
is to rename one of the methods calling. i'll make a post when
This seems like a bug, I am currently busy trying to get AOP 2.0 alpha ready,
but will try to get this in before then.
http://jira.jboss.com/jira/browse/JBAOP-284
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968397#3968397
Reply to the post :
http://www
Actually I was wrong to say that it was reading SUBPOJO.field. It's actually
reading POJO.field. The problem is that when I try to write to SUBPOJO.field,
the code is rewritten by jboss AOP in such a way that it writes to POJO.field
instead.
The problem seems to be the mechanism used to interc
