------- Additional Comments From [hidden email] 2005-06-12 05:40 -------
(In reply to comment #34)
> (In reply to comment #32)
> > 1) Invocation of constructor in createLogFromClass
> I think this should be fixed in LogKitLogger rather than in LogFactoryImpl.
> It's difficult to tell these apart, but I would suggest specifying (in the Log
> interface javadoc) that a NoClassDefFound or an ExceptionInInitializerError
> should indicate "not available" while an InvocationTargetException indicates
> available-but-broken. This is the approach that I took with Jdk14Logger, where
> there is a dummy variable that forces an ExceptionInInitializerError if
> java.util.logging.Level is not available. I expect a similar thing could be done
> with LogKitLogger...
+1. I was about 65% of that opinion when I added that big comment in the patch :)