Sam Ruby wrote:
> Either:
>
> 1) We need to make the abstraction for logging independent of Turbine and a
> Jakarta "standard".
Logging system needs some means of configuration. If we deteach it from
Turbine, it will need a separate config file, and some way of finding
it.
In servlet env, this probably means accessing ServletContext... I don't
see a clean way of dealing with that.
> 2) Standardize Jakarta on a single concrete implementation
> (jakarta-log4j?).
Would be a number 1 candidate if we figured out configuration issues...
> or
>
> 3) as you stated, not do logging in reusable components. (YUCK).
I don't think so :-)
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
