[Jboss-dev-forums] [Design of JMX on JBoss (JBoss/JMX)] - Re: Setting the thread context class loader on mbean op disp

[<sco...@jb...>]

Yes, there is a red flag issue once you have a service trying to interact with multiple class loaders, but it should be possible if designed for this. The only classes that are subject to linkage errors and class cast expections are those that show up in the service's interface (ignoring any bugs due to caching of types by the class loader or other layers). This of course means a detyped interface in general. An interesting question is, if such an interface was modifed to use generics, is there any type leakage. As far as I understand the generics type nullifcation mechanism, the type binding would be in the client usage context and therefore its class loader context, but this is something I would like to verify, and verify that it works with type reloading in the client class loader.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3876187#3876187

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3876187