Bugs item #602828, was opened at 2002-08-31 05:39 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=602828&group_id=22866
Category: JBossMX Group: v3.0 Rabbit Hole Status: Open Resolution: None Priority: 5 Submitted By: Scott M Stark (starksm) Assigned to: Nobody/Anonymous (nobody) Summary: Need a shared class loader notion Initial Comment: There are two problems that show up because of the current UCL per deployable jar. 1, if classes in a package are split across jars then access of package private methods between the jars fails. 2, if you have a jar of classes version 1 and a patch jar that contains version 2 classes that replace some of the version 1 classes, we have no way to specifiy that classes in the patch jar should be loaded ahead of the version 1 classes. I think what we need is the notion of a shared class loader per top level deployment unit that handles all jars referenced via manifests. This would honor the ordering of jar references so that one could control loading of patches. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=602828&group_id=22866 ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
