Hi All,
That's seems to me like the best idea.
Maybe all the master minds behind log4j, logkit and
someone from jdk 1.4 logging facilities can produce a
set of common interfaces ( factories, main
abstractions - maybe with some jndi ) that can
abstract the Logger capabilities and let the end user
choose an implementation.
Do you guys think this is at all possible to do?
Thanks, CC
--- Berin Loritsch <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> >
> > I think LogKit and Log4J are both great and
> external interface is pretty similar.
> >
> > How about Avalon providing a logger service that
> maps to LogKit and can also map to Log4J. That way a
> user can configure whatever one likes.
> > It may be good to have LogKit as a separate
> project and peer of Log4J. Let the non Avalon users
> pick what they like. I personally find LogKit
> Simpler and easier to follow but Log4J more
> powerful. There is a time and place for both and why
> choose one over other.
>
>
> My whole point is that I want something like
> LogKit's Logger interface available
> that both Log4J and LogKit can implement. If
> necessary, we can even create a wrapper
> for JSR Logging (which is botched). That way Avalon
> Framework is agnostic of the
> underlying Logging technology, and can be used in
> any setting. Avalon Phoenix will
> most likely remain LogKit central--and that is to be
> expected. I want a Loggable
> interface that is not tied to a specific Logging
system.
> ATTACHMENT part 2 application/x-pkcs7-signature
name=smime.p7s
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
