Class loading isolation with overrides is the correct approach, but the deployment should have have any java.* or javax.* classes in the deployment as these cannot be overriden. Apparently most other class loading approaches just ignore attempts to load such classes and so don't care about their existence. Currently we don't have a notion of classes that cannot be loaded from the deployment so they need to be removed to work with scoped class loading.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861580#3861580 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861580 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
