Richard,
The commons-logging-<impl>.jar approach you suggested earlier will throw an exception if <impl> is not available which should be perfectly fine because if the user explicitly puts commons-logging-<impl>.jar in her classpath, then it means that she wants <impl> around.
I quite like it.
It lends it's self well to this, but it's not sufficient. The requirement is for this behavior to be exhibited by JCL, for example when Log4j is configuted, but not available on the classpath.
-- Ceki G�lc�
The complete log4j manual: http://www.qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
