You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@s-und-n.de> on 2003/08/29 14:02:24 UTC
[Vote] Move from LogKitManager to LoggerManager
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).
So, please vote on the change.
and please vote if this is a change for 2.1.1 or 2.2.
Thanks
Carsten
Re: [Vote] Move from LogKitManager to LoggerManager
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
Gianugo Rabellino wrote:
> 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
RE: [Vote] Move from LogKitManager to LoggerManager
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Gianugo Rabellino wrote:
>
> 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...
>
Whereever a LogKitManager is currently created this code is replaced
with creating a LoggerManager, this is mainly the servlet, the cli code
and Cocoon.java and that's it. So only code relying on these three
classes and their internal implementation should be affected.
Carsten
Re: [Vote] Move from LogKitManager to LoggerManager
Posted by Gianugo Rabellino <gi...@apache.org>.
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...
Ciao,
--
Gianugo Rabellino
Pro-netics s.r.l. - http://www.pro-netics.com
Orixo, the XML business alliance - http://www.orixo.com
(Now blogging at: http://blogs.cocoondev.org/gianugo/)
Re: [Vote] Move from LogKitManager to LoggerManager
Posted by Upayavira <uv...@upaya.co.uk>.
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).
>
>So, please vote on the change.
>
>and please vote if this is a change for 2.1.1 or 2.2.
>
>
>Thanks
>Carsten
>
+1 for 2.1.1
And I will happily implement this in CocoonBean (which has changed since
the patch was written).
Upayavira
Re: [Vote] Move from LogKitManager to LoggerManager
Posted by Sylvain Wallez <sy...@anyware-tech.com>.
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).
>
>So, please vote on the change.
>
>and please vote if this is a change for 2.1.1 or 2.2.
>
>
+1 in 2.1.2 !
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
Re: [Vote] Move from LogKitManager to LoggerManager
Posted by Ugo Cei <ug...@apache.org>.
Carsten Ziegeler wrote:
> So, please vote on the change.
>
> and please vote if this is a change for 2.1.1 or 2.2.
+1 on 2.1.1.
Ugo