I think that is too simplified but the seperation between the CL invoked to do the class loading by threads vs the UCLs in the repository actually used to load code in a single threaded fashion is what I was proposing to simplify the locking issues.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Bill Burke" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, May 31, 2002 10:41 AM Subject: RE: [JBoss-dev] ClassCircularityError - PROBLEM FOUND ! > I hope I'm not being really stupid here. Couldn't you have one master class > loader that delegated to a UCL. Then you wouldn't need all this funky > locking and hacks and workarounds. Switch the ULR and UCL. ULR delegate to > UCL instead of the other way around.... > > Again, maybe I'm just ignorant of the code. > > Bill > _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
