Quite a nasty problem... I did some digging with the debugger and found that that object which it's saying it can't find interfaces for is a dynamic proxied object. Quite irritating that it doesn't just ignore and carry on. Not quite sure why it works when running outside of the container though. Btw, the object which I had the same problem is the SessionFactory object which is proxied by spring/jboss. Not quite sure which. An efficient to block this object from being scanned by spring's AOP would be great, blocking each individual method is the only way I see it working. I think the spring AOP first resolves the method and then moves on so if the method resolution fails, then it goes onto the next method. Again, why such a problem would cause a complete failure, I don't know. It would also be interesting to see how spring's AOP/aspectJ behaves with a proxied object. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013650#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...