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...@sundn.de> on 2001/08/07 15:00:35 UTC
[C2]: Simplyfying log configuration
The configuration of the log is currently done in the web.xml.
This includes the log level, the log file name etc.
What do you all think about moving this configuration to the
cocoon.xconf? This would allow any change to take effect
immediately after it was changed when cocoon is reloaded.
And personally I think it would make things a little bit easier for
users as they must only deal with one configuration file.
Carsten
Open Source Group sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de mailto: cziegeler@sundn.de
================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2]: Simplyfying log configuration
Posted by giacomo <gi...@apache.org>.
On Tue, 7 Aug 2001, Berin Loritsch wrote:
> Carsten Ziegeler wrote:
> >
> > The configuration of the log is currently done in the web.xml.
> > This includes the log level, the log file name etc.
> >
> > What do you all think about moving this configuration to the
> > cocoon.xconf? This would allow any change to take effect
> > immediately after it was changed when cocoon is reloaded.
> > And personally I think it would make things a little bit easier for
> > users as they must only deal with one configuration file.
>
>
> :)
>
> I already proposed this a week and a half ago. William Vambenepe
> from hp.com has volunteered to start this effort. This will also
> help us separate different categories into different logtargets.
The latest proposal I've heared on the Avalon list are magic attribute
(like the pool-max ones) used in the xconf file to define
logger/category/level on a component basis (but there are some
limitations in LogKit to realize different loglevels on the same
Category)
Giacomo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: [C2]: Simplyfying log configuration
Posted by Berin Loritsch <bl...@apache.org>.
Carsten Ziegeler wrote:
>
> > Berin Loritsch wrote:
> >
> > Carsten Ziegeler wrote:
> > >
> > > The configuration of the log is currently done in the web.xml.
> > > This includes the log level, the log file name etc.
> > >
> > > What do you all think about moving this configuration to the
> > > cocoon.xconf? This would allow any change to take effect
> > > immediately after it was changed when cocoon is reloaded.
> > > And personally I think it would make things a little bit easier for
> > > users as they must only deal with one configuration file.
> >
> >
> > :)
> >
> > I already proposed this a week and a half ago. William Vambenepe
> > from hp.com has volunteered to start this effort. This will also
> > help us separate different categories into different logtargets.
> >
> Ups, must have missed that (I got app. 2000 emails during my vacation...)
> Great, when is it finished...?
Don't know, William got back to me a couple days ago--so he probably just
started.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2]: Simplyfying log configuration
Posted by Carsten Ziegeler <cz...@sundn.de>.
> Berin Loritsch wrote:
>
> Carsten Ziegeler wrote:
> >
> > The configuration of the log is currently done in the web.xml.
> > This includes the log level, the log file name etc.
> >
> > What do you all think about moving this configuration to the
> > cocoon.xconf? This would allow any change to take effect
> > immediately after it was changed when cocoon is reloaded.
> > And personally I think it would make things a little bit easier for
> > users as they must only deal with one configuration file.
>
>
> :)
>
> I already proposed this a week and a half ago. William Vambenepe
> from hp.com has volunteered to start this effort. This will also
> help us separate different categories into different logtargets.
>
Ups, must have missed that (I got app. 2000 emails during my vacation...)
Great, when is it finished...?
Carsten
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2]: Simplyfying log configuration
Posted by Berin Loritsch <bl...@apache.org>.
Carsten Ziegeler wrote:
>
> The configuration of the log is currently done in the web.xml.
> This includes the log level, the log file name etc.
>
> What do you all think about moving this configuration to the
> cocoon.xconf? This would allow any change to take effect
> immediately after it was changed when cocoon is reloaded.
> And personally I think it would make things a little bit easier for
> users as they must only deal with one configuration file.
:)
I already proposed this a week and a half ago. William Vambenepe
from hp.com has volunteered to start this effort. This will also
help us separate different categories into different logtargets.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2]: Simplyfying log configuration
Posted by Donald Ball <ba...@webslingerZ.com>.
On Tue, 7 Aug 2001, Carsten Ziegeler wrote:
> The configuration of the log is currently done in the web.xml.
> This includes the log level, the log file name etc.
>
> What do you all think about moving this configuration to the
> cocoon.xconf? This would allow any change to take effect
> immediately after it was changed when cocoon is reloaded.
> And personally I think it would make things a little bit easier for
> users as they must only deal with one configuration file.
+1
- donald
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2]: Simplyfying log configuration
Posted by giacomo <gi...@apache.org>.
On Tue, 7 Aug 2001, Carsten Ziegeler wrote:
> The configuration of the log is currently done in the web.xml.
> This includes the log level, the log file name etc.
>
> What do you all think about moving this configuration to the
> cocoon.xconf? This would allow any change to take effect
> immediately after it was changed when cocoon is reloaded.
> And personally I think it would make things a little bit easier for
> users as they must only deal with one configuration file.
Well, I think you cannot remove the logger out of the servlet because
you need it during CM setup. But afterwards the Cocoon class can change
the LogTargets/Formats using a LogManager component (I think I'm
repeating Berins proposal more that once today :)
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org