avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Berin Loritsch <blorit...@apache.org>
Subject Re: Common Logging Interface
Date Wed, 07 Nov 2001 21:58:39 GMT
Richard Sitze wrote:
> >> 2.  Make the minor mods to LogKit and Log4J
> >>     (the two predominant open-source logging API's)
> >>     to eliminate overhead of wrappers entirely when
> >>     used with the framework...
> >
> >Here is the deal with that approach:
> >
> >Requiring a supposedly self-contained jar to implement interfaces from an
> >external project now REQUIRES all users of the jar to now incorporate that
> >other jar.  Either that, or include the other jar inside the
> self-contained
> >jar.  That would mean that both LogKit and Log4J would be required to
> include
> >the contents of the shared interface jar.  Can you imagine the classloader
> >issues?
> Why?  The framework guarentees that only one of them gets loaded into the
> JVM..
> the other isn't needed.

Two reasons:

1) Compilation
2) Classloader

If you implement an interface, it MUST be in the same classloader--otherwise
you get a ClassNotFoundError, and logging will not be available.  UNLESS the
required jar is available.


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

To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>

View raw message