On 9 Dec 2004, at 20:21, Richard Sitze wrote:
<snip>
The fundamental problem with the current factory is that it is dependent on "passively" identifying a logging implementation.
We propose one solution below, but would ask a more general question: any new bright ideas?
apologies for being so late on this one :(
this idea isn't particular new (though it may be new to some people) but it might be new to some people on this thread.
the passivity is a symptom of commons logging being too big, too complex and too tightly coupled to the needs of applications run in containers and yet not sophisticated enough. IMO the commons logging API could and should be reduced to one interface and one public class each with no dependencies on anything about java 1.0.
everything else, all the sophisticated configuration can be achieved by byte-code engineering: doping the appropriate jars so that the calls are wired correctly. there is certainly an amount of resistance to byte code engineering from some quarters but after a long hard slog, i really think that this is the only way that the initial aims of the component can be achieved.
i've been hoping to find some cycles to get something along these lines up and running but sadly, i don't seem to find enough time these days...
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
