|
From: | mark at gcc dot gnu dot org |
Subject: | [Bug classpath/26668] java.util.logging bugs |
Date: | 15 Mar 2006 13:41:05 -0000 |
------- Comment #4 from mark at gcc dot gnu dot org 2006-03-15 13:41 ------- Comment on 1. The LogManager only looks up classes in the system class loader. My patch modifies it to also check the context class loader if nothing is found in the system class loader. This is necessary for third party logging managers to work at all. Agreed. This makes sense. But I would try the context class loader first and fall back to the system class loader if that fails. That is what other core library code also does. Also naming the method forName() is a little confusing (since there is also Class.forName). I would just inline that part into createInstance(). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26668
[Prev in Thread] | Current Thread | [Next in Thread] |