Martin Poeschl <[EMAIL PROTECTED]> writes:
>thanx to Ceki and Nicola for their posts!
>after reading all the post to the logging question it's still not clear
>how we can solve the problem.
>turbine is not only the turbine.jar .. we use velocity,
>commons-packages, ...
>all this packages use different logging packages (log4j,
>commons-logging, ...)
Ok, even on the risk of making myself being unpopular again...
We have three major building blocks for Turbine applications ATM. These
are "Turbine", "Velocity" and "Torque".
"Turbine" currently uses the LogService. This is definitely going to die.
"Velocity" uses some possible loggers, one of them is log4j
"Torque" uses log4j
So I _still_ propose to integrate my 10 lines change to Turbine.java
which activates log4j as the primary logging facility for Turbine,
initialized commons-logging to actually use log4j and the convert
every Log.<xxx> reference in the Turbine code to log.<xxx>
I do have this code not only here and working bug actually deployed
and in production. Contrary to the belief of some Avalon and log4j
developers, none of my Tomcats has melted down (yet... :-) )
This might not be the ideal solutions but IMHO it is a working
solution until the religious wars about CoC and IoC models cease.
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]>
