> -----Original Message-----
> From: Richard Sitze [mailto:rsitze@us.ibm.com]
>
> 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.
Err, "goals are" antagonistic. (orthagonal simply means unnassociated,
can go either way).
--
To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
|