Kurt Schrader <[EMAIL PROTECTED]> writes:
>On Wed, 11 Dec 2002, Nicola Ken Barozzi wrote:
>> I'm not suggesting that you use Logkit, but the Avalon logging interface
>> and facades. the Logger is part of the Avalon lifecycle, and it's very
>> important, also from a security perspective, that it's given by the
>> container, not gotten by the Component, and makes management of it easier.
>Does it tie Turbine to using Avalon exclusively or is it like
>commons-logging with some extra hooks into Avalon?
Folks,
please. We do not try to build Avalon-light or an Avalon clone.
Staring at foreign code and rebuilding every interface from another
project will not help us.
Compared to Avalon, Turbine is really lightweight and simple. I'll try
to keep it that way. If we can use synergies with Avalon, fine. If
not, well, if you need all the features of Avalon, why not use Avalon
in the first place? We do not try to be an end-all, be-all solution
which replaces all other web-application frameworks. We do not need to
be "best-of-brand" in every category. We're not even trying to
compete. :-)
I see logging for Turbine as a way to offer a centralized, easy to use
and flexible facility for applications and services. All this does
commons-logging in conjunction with log4j (or JDK 1.4) offer.
I'll keep this code simple, hardcoded and out of the lifecycle
code.
Reason: You'll end up with a mess like in the current Turbine. What if
you want to log messages before your ServiceBroker/ComponentContainer
has even started? Remember the posting about the stratum message
popping out of Stdout because of this. Logging is simply the second
thing that we will set up right after startup (First thing is reading
the conf because we need this for configuring the logging). That's it.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
