The Aspect service has a flag to ignore transformation errors. I had to have this
switch because a bunch of Apache classes use their own classloaders and don't hook
well into Javassist's class locator.
Do you have a simple testcase you can send me to reproduce the error (with hot deploy
of pre
Thanks for the quick reply.
I just sent you a testcase by e-mail, which hopefully will recreate the exception at
your end.
Peter
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837416#3837416
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=
didn't get a chance to look at this before the beta3 release. Sorry. I'll take a
look soon.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3837695#3837695
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3837695
--
This issue is very similar to what I had posted earlier and the solution that I
resorted to was during the undeploy/re-deploy time call
AspectManager.getAdvisors().remove(instrumentedClassName).
However Bill have'nt tried the newer version of AOP yet in which you had mentioned
that I could avoi
