On 4/3/02 3:18 PM, "Berin Loritsch" <[EMAIL PROTECTED]> wrote:
>> -----Original Message----- >> From: Morgan Delagrange [mailto:[EMAIL PROTECTED]] >> >> --- "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote: >>> On 4/3/02 2:45 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> >>> wrote: >>> >>>> On Wed, 3 Apr 2002, Geir Magnusson Jr. wrote: >>>> >>>>> Yes, that's true. I didn't realize that it >>> o.a.c.l was actually a logging >>>>> framework.... I thought it was an interface we >>> could write to in order to >>>>> isolate ourselves from changing logger >>> preferences... >>>> >>>> It's a logging API, with interfaces you can use to >>> isolated from the >>>> logger implementation. >>>> >>> >>> However, it seems that the Log.getLogger(foo) >>> pattern is what people have to >>> use, or are expected to use? >>> >> >> Is that not also the case with Log4J and JDK 1.4? >> Only the Avalon logger has a notion of IoC AFAIK. It >> seems odd to be supporting IoC logging in >> commons-logging, when we know that all of our other >> components will not be able to utilize it. > > My point exactly. > > Commons Logging should be for all modules that do not > use IoC. > Commons logging should be for all modules that want a generic logging interface. In my opinion anyway... :) > For those that do need IoC, they either need to use Avalon or > create their own framework. (Hopefully, use Avalon ;P ) > And in that framework, can they have their components use the generic commons interface for logging? -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting "He who throws mud only loses ground." - Fat Albert -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
