On 4/3/02 2:47 PM, "Richard Sitze" <[EMAIL PROTECTED]> wrote:
> I went round-and-round with Berin a few months ago before he convinced me > on this point. The LogKit API provides a simple framework based on IoC > that "wraps" various loggers. It became clear that adding the popularly > used "pull" (Log4J, JDK 1.4, and other loggers) model to the Avalon LogKit > was counter to their design goals. At about the same time the commons > logging API was released. > > Perhaps what we need is pointers (in both components) to the logger > supporting the "other" philosophy: > > If you want "pull", use commons logging. > If you want "push" and IoC, use the Avalon LogKit. > > And again, DON'T propose trying to merge the two, their goals are > orthogonal. > But why do I have to use LogKit for IOC? It's a general idea - shouldn't be tied to one logger impl.... -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting Age and treachery will always triumph over youth and talent -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
