James Taylor <[EMAIL PROTECTED]> writes:
>The problem is that the avalon way and the commons-logging way are quite
>different.
>The avalon way inverts control so that the container provides logging to
>each component. In the commons-logging / log4j way each class requests a
>logger from a factory (ick).
I still see no reason, why a commons-logging factory should not be able
to return the container supplied logger reference to the application.
like this:
"Container provides application with logging facility".
"Turbine starts up. Notices, that it got a logging facility from the
container. Registers it".
User uses "Log log = LogFactory.getLog("foo")". Commons Logging
has been configured to return a log object provided by the container-
provided log facility.
And the user never notices that he has not a "Turbine configured log4j
logging" but a "container provided enterprise logging facility".
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]>
