Dispatcher:118 is a piece of code where it makes a final attempt to invoke the method, so
it tries it by itself. This is bound to fail, because Dispatcher has no knowledge of the
right class loader context, only the EJB container knows this.
ClassProxyHack came into being because EJBContainer used to be an AOP ClassContainer and
thus it remoted it's governing class (/bean class) and not itself. The current
EJBContainer still has that same remoting characteristic.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168260#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...