[ot] Re: Removal of project

[Jon Stevens <jo...@latchkey.com>]

on 11/2/01 1:24 PM, "Berin Loritsch" <bl...@apache.org> wrote:

> That said, Avalon Framework now allows you to work with
> other Logging toolkits than just LogKit.

Cool! I'm just curious, how is that accomplished? Through another set of
interfaces?

-jon


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: [ot] Re: Removal of project

[Berin Loritsch <bl...@apache.org>]

Jon Stevens wrote:
> 
> on 11/2/01 1:24 PM, "Berin Loritsch" <bl...@apache.org> wrote:
> 
> > That said, Avalon Framework now allows you to work with
> > other Logging toolkits than just LogKit.
> 
> Cool! I'm just curious, how is that accomplished? Through another set of
> interfaces?

Yep.  The use of the logger is completely separate from it's configuration,
so we only provide the client interface (i.e. the debug("message", exception)
methods).  We also supply three wrapper classes (one for LogKit, one for
Log4J, and one for JDK 1.4--if installed).

Lastly, since Avalon uses the Inversion of Control pattern, the Logger is
handed to classes that implement the LogEnabled interface.

Anything more than what is included in the framework goes beyond simply
using the Logging implementation.


-- 

"Those who would trade liberty for
 temporary security deserve neither"
                - Benjamin Franklin

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>