I must correct myself! We have a principle problem, unfortunately, for which I do not have an immediate answer right now:
Actually, instead of synchronized(classLoaders) in ServiceLibraries, there would be the need to *atomically* synchronize on all instances of the set in order not to interfere with the ClassLoader.loadClassInternally() calls. But this is not possible with the Java synchronization mechanism, AFAIK. Puzzling, CGJ (BTW: If somebody would offer Voodoo-puppets of SUN developers in the jboss-store, you could make a fortune! If you would additionally provide JBoss-needles, you could even make a bigger one!) -----Ursprüngliche Nachricht----- >Von: Sacha Labourey [mailto:[EMAIL PROTECTED]] >Gesendet: Montag, 1. Oktober 2001 15:04 >An: Jung , Dr. Christoph >Betreff: RE: Java Classloaders document >Christoph, >I've just read your answer and as I am not yet up-to-date with the new JBoss >classloading mechanism, can't be very efficient at commenting your idea... >Consequently, I am very confident in what you suggest ;) >No, in fact, what you suggest seem very very possible. I may try to >synchronize a method from your loading mechanism to see if it solves the >problem. Which part should I synchronize? >Thank you for your very effective help. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
