Carsten Ziegeler wrote:
Triggered by the recent discussions about using log4j, I propose that we move from the deprecated LogKitManager to the new LoggerManager. This will make using log4j much easier (and I would implement that then next).
There is a patch for the move already in bugzilla: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21730
But: this is an incompatible change (however the impace should be very small).
Please give us more details of the impact on both Cocoon core and external components. Loggable to LogEnabled meant a hell of a mess to me in the past, I don't want to go down that path again...
AFAIK, this will affect all components implementing LogKitManageable. Or does the compatibility layer in ECM take care of this ?
Sylvain
-- Sylvain Wallez Anyware Technologies http://www.apache.org/~sylvain http://www.anyware-tech.com { XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects } Orixo, the opensource XML business alliance - http://www.orixo.com
