On Thursday 10 February 2005 03:34, Ceki G�lc� wrote: > nless the ugli-xxx.jar file is corrupt, UGLI cannot never cause bugs of > Type-I, Type-II or Type-III for the simple reason that all the required > files are bundled together in the ugli-xxx jar file. UGLI's LoggerFactory > only uses the class laoder that loaded LoggerFactory itself to instantiate > other classes. In future versions of UGLI, the binding will done at compile > time, so such questions won't even need to be asked.
Hmmmm.... So you are saying, that if I for each commons-logging.jar includes log4j.jar in the same classloader, I still have TypeII problems?? That is a case that your page doesn't cover, and right now I can't see that something bad would happen (in parent-first CLs. IMHO Child-First are plainly bad.), and would be interested to be informed of such scenario. Don't get me wrong, I don't like JCL, but IMHO we are dealing with 3 different types of problems; 1. Architectural. 2. Deployment and misconfigurations. 3. Bugs. And it is at times difficult to separate them apart. I can probably agree that UGLI addresses 2 and 3. 3. is IMO a non-issue, and just a matter of kicking the JCL's butt. 2. is the matter of UGLI forcing the proper bundling. 1. is what really interests *me* as a 'container author'. Cheers Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
