From: <sco...@jb...> - 2005-05-02 14:47:46
|
The mbean invokers set the current thread context class loader to that of the mbean on op dispatches. This is what you want in general, but if the mbean represents a shared service like a cache that interacts with other isolated deployments, the thread context class loader needs to be that of the caller. We need a notion of a chained thread context class loader which would combine the incoming thread context class loader with that of the mbean service as its parent to allow for visibility into both layers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876145#3876145 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876145 |