cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Morrison, John" <>
Subject RE: Porting Cocoon Logging to Log4j - Proposal and Discussion
Date Thu, 28 Aug 2003 09:56:04 GMT
I for one would be -1 on this.  Cocoon relies heavily on Avalon, it
makes IMNSHO little sense when Avalon supports multiple logging
mechanisms to rip it out and recode.


Robert Simmons wrote:
> Actually, I was proposign the removal of the avalon logging mechanism
> completely. 
> -- Robert
> "Carsten Ziegeler" <> schrieb im Newsbeitrag
>> The Avalon Logging can be changed to use Log4J. Currently the usage
>> of the LogKit is hard-coded in Cocoon. I added the possibility to
>> configure which logging framework you want to use to the avalon
>> core, but never had 
> time to test
> it.
>> If this is working, only minor changes have to be made to Cocoon
>> (changing three or four lines of code) and you can use Log4j in
>> Cocoon. 
>> Carsten
>>> -----Original Message-----
>>> From: news []On Behalf Of Robert Simmons
>>> Sent: Thursday, August 28, 2003 11:32 AM
>>> To:
>>> Subject: Porting Cocoon Logging to Log4j - Proposal and Discussion
>>> One of the major implementaiton complaints I have about
> Cocoon is its
> lack
>>> of Log4J logging functionality. Log4j, is without a doubt the best
>>> logging package for java. No other package can even hope to compare
>>> to it. If Cocoon was built to use Log4j instead of the avalon
>>> logging mechanism, it would gain an enormous amount of
>>> functionality that it lacks now. 
>>> Personally, when working in a production environment, I dont want
>>> my log files to be put into direcroies in my web app. Id rather
>>> have them forwarded to a central log accumulation server or even
>>> sent out via JMS. Log4j allows this and many more configurations.
>>> Furthermore, it allows you to turn on and off logging on individual
>>> components with ease. Finally, Log4J is used in so many other
>>> products that it is a recognized standard logging mechanism that
>>> many organizations and even network engineers are quite familiar
>>> with.  
>>> Therefore, I think Cocoon should migrate to Log4j. In order to
>>> contemplate this, its important that we discuss the complexities of
>>> it in the following quesitons.
>>> 1) Why has this not already been done? Is it a question of a lack of
>>> manpower or expertise? If so then I as well as others
> would most likely
> be
>>> happy to volunteer time to accomplish it.
>>> 2) How difficult is it to rip out the avalon logging from
> the cocoon
> core
>>> components? Im no avalon expert so I couldnt answer this myself.
>>> 3) Is there standard expressions that can be used for locatting
>>> logging lines in cocoon? 
>>> 4) Do we upgrade some of the blocks or leave them as is and only
>>> upgrade core cocoon? 
>>> I would be interested in comments and opinions.
>>> -- Robert

Information in this email and any attachments are confidential, and may
not be copied or used by anyone other than the addressee, nor disclosed
to any third party without our permission. There is no intention to
create any legally binding contract or other binding commitment through
the use of this electronic communication unless it is issued in accordance
with the Experian Limited standard terms and conditions of purchase or
other express written agreement between Experian Limited and the recipient
Experian Limited (registration number 653331)
Registered office: Talbot House, Talbot Street, Nottingham NG1 5HF

View raw message