Bachran, Michael wrote:
> Hi everybody,
>
> Unfortunately I missed the invention of the LogEnabled stuff?
>
> Currently I am using the Framework along with the ExcaliburComponentManager
> (ECM) (Release 4.0). Along with the ECM comes LogKit.
> As the project started using Log4J I am planning to shift to LogKit now to
> get rid of one of two loggers.
>
> I am currently wondering if LogEnabled will simply replace Loggable (same
> for abstract classes) and if this has something to do with shifting to
> compatibility with the upcomming JDK1.4 Logging API.
> I also want to use the LogKitManagement along with LogKit.
> At least I would like to know if the interface is stable or I should wait
> with shifting till the changes have been applied.
Rest easy Michael.
The LogEnabled and Logger interfaces is a straight replacement for the
Loggable interface. The difference is that you are now not _tied_ at the
framework level. The ExcaliburComponentManager is still LogKit centric,
and will remain so for a while.
The interface for the Framework Logger interface is exactly the same as
the public portion of the LogKit interface. Our first loyalty is to the Avalon
LogKit package--although we do not want to alienate potential users who don't
want to use it. In the end, you now have a public interface that is consistent
no matter what Logging package you use.
--
"Those who would trade liberty for
temporary security deserve neither"
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
