Gérard Vandome wrote:
Madl Alfred wrote:
Hi !
What about providing an "adapter" implementation for common-logging API to the monolog API ? The idea would simply be to "redirect" calls made to the common-logging API to monolog and in fact doing configuration and logging level setting in monolog (I like the Jonas Web Admin GUI for setting loglevels !).
It can be a good solution, if it doesn't introduce overhead.
I cc the architecture mailing list as I think the best is to move the discussion there.
This might work, but my opinion is we should move logging to
common-logging.
This discussion has already taken place in the ObjectWeb architecture
team, and many of us (not yet all ;) believe Monolog is a dead end now.
We do not need one more logging technology, Apache has gained the
required momentum, not us. Also, some of our products include or use
Apache modules, that already use commons-logging...
Of course, the JonasAdmin problem remains: the question is, do the
Jonas team plan to move to commons-logging some time ? (Gerard seems to
envisage it, at least...)
Providing the wrapper you suggest could be considered a temporary
solution, then...
Regards,
Pierre-Yves Gibello - ExperLog
Of course the implementation of such an adapter would have to be VERY efficient in order to avoid unnecessary overhead for logging calls !
Just an idea.
Alfred
-----Ursprüngliche Nachricht-----
Von: Gérard Vandome [mailto:gerard.vandome@xxxxxxxxxxxxx]
Gesendet: Donnerstag, 23. Oktober 2003 14:14
An: Madl Alfred
Cc: christophe.ney@xxxxxxxxxxxxx; Raicevic Igor; FRANCOIS EXERTIER; Andre Freyssinet; Jeff Mesnil; FRANCOIS EXERTIER
Betreff: Re: Enhydra and Jonas
Madl Alfred wrote:
Hi !
Christophe told me, you could possibly help me:
We would have some technical/architecture oriented questions for
integrating Enhydra 6.0 (the Enhydra application framework) into
Jonas/Tomcat in the area of "logging".
Jonas itself uses the "Objectweb monolog API"
Tomcat itself uses the "Apache common-logging API"
Enhydra EAF has ist own logging API for web applications (currently
implemented for log4j)
I would like to discuss the relationship of these APIs and possible
architecture scenarios in this area for the Enhydra/Jonas integration.
Do you know the best guy to talk to for these questions ? Could I call
him to discuss that ?
It is a very good question, and I am not happy at all with the current JOnAS situation which is still more complicated: JOnAS is also integrating Axis (which are using common logging) and JORAM and JORM (which are using Monolog). JOnAS will soon integrate JOTM (instead of the JOnAS embedded transaction manager) and C-JDBC which are using common logging..
Just an history to explain the current situation:
-ObjectWeb provide Monolog to be able to use either Log4J or JDK logger -then Apache provide Common-Log with the same goal
The curent ObjectWeb recommandation is to use Monolog, but my personnal preference would be to move everything in JOnAS to common-logging. I cc François, Andre and Jef who have more technical arguments....
Gérard Vandôme
ObjectWeb Consortium www.objectweb.org Gerard.Vandome@xxxxxxxxxxxxx +33 (0)4 76 29 76 25
--
Gérard Vandôme
ObjectWeb Consortium www.objectweb.org
Gerard.Vandome@xxxxxxxxxxxxx +33 (0)4 76 29 76 25
|
