On 17 Dec 2004, at 01:56, Richard Sitze wrote:
robert burrell donkin <[EMAIL PROTECTED]> wrote on 12/16/2004 04:38:34 PM:
<snip>
the solution i've been considering is to separate the base application-environmental configuration from the sophisticated discovery process required to ensure proper isolation in complex managed server environments. (i'm not going to describe this in detail right now: i should post a code example but i'm tired so that'll have to wait.)
I will eagerly await, and will compare your thoughts to what is described
in the original proposal. For reference, please note that the proposal
can be found here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=32618
i've added some thoughts onto some new wiki pages linked from http://wiki.apache.org/jakarta-commons/Logging.
where does byte-code engineering come in? well, there are certain
things that users want that are just not going to be feasible no matter
how sophisticated a discovery process is employed. too much complexity
leads to fragility in the discovery code: providing rewiring at the
byte-code level would allow users great control and relieve the
commons-logging development team of the burden of creating every more
complex discovery code.
And other teams... this *must* be addressed independently from Logging.
+1
- robert
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
