If you add these lines to the POJO example, you should get a nice stack trace...
from an assist.NotFoundException that starts with:
It appears that calling
Introspector.getBeanInfo(pojo.getClass()); generates the mil.army.perscom.ASBS.aop.POJOBeanInfo class on the fly. Then Javassist can't find a matching a class file. Is there any way to get rid of the big stack trace?
I'm writing this because you get the same thing when you use Log4j with property file configuration.
After looking the code, it seems that some Exception printStackTrace are left into the code for trace purpose, even when the Exception is rethrown.
I hope these statement will be removed in the next releases.