On Wed, 8 Aug 2001, Leo Sutic wrote:
> Peter, Berin,
>
> how will this work with individual log levels for each
> logger/category/channel?
>
> If one adds two properties: logger and loglevel, like this:
>
> <component role="com.foo.Component"
> class="com.foo.DefaultComponent"
> logger="foo"
> loglevel="DEBUG"/>
>
> Is there a problem when having multiple components using the same logger?
>
> <component role="com.foo.Component"
> class="com.foo.DefaultComponent"
> logger="foo"
> loglevel="DEBUG"/>
>
> <component role="com.foo.Component2"
> class="com.foo.DefaultComponent2"
> logger="foo"
> loglevel="ERROR"/>
I don't really like specifying the LOGLEVEL in the
component configuration. I think this is something that has to be
specified at the class instantiating the loggers. Do you see yourself
changing all loglevels in the config file when you deploy it for
production?
Giacomo
>
> If the two components share the same logger instance, I don't see how this
> can work. Of course, the fact that I have no idea of how the contract for
> getChildLogger is in respect to multiple children with the same subcategory.
>
> /LS
>
> > -----Original Message-----
> > From: Peter Donald [mailto:[EMAIL PROTECTED]]
> > Sent: den 8 augusti 2001 15:22
> > To: Avalon Development
> > Subject: Re: JDK1.4 logging vs. LogKit
> >
> >
> > On Wed, 8 Aug 2001 22:42, Berin Loritsch wrote:
> > > Peter Donald wrote:
> > > > Hi,
> > > >
> > > > On Wed, 8 Aug 2001 06:10, giacomo wrote:
> > > >>I have to confess that I don't know how this works in all my
> > components
> > > >>that are based on AbstractLoggable and have the logger passed in from
> > > >>ExcaliburCM.
> > > >
> > > > Just looked at ExcaliburCM and it doesn't really support
> > separate loggers
> > > > per component. Berin what do you think of adding an extra attribute to
> > > > component definition so that you can specify name of logger.
> > Then later
> > > > on instead of doing
> > >
> > > I was thinking about that before. We need to add an attribute to the
> > > component definitions (probably "logger"). Something like this
> > to specify
> > > it:
> > >
> > > <component role="com.foo.Component"
> > > class="com.foo.DefaultComponent"
> > > logger="foo"/>
> > >
> > > The attribute name is negotiable ;).
> >
> > logger works for me.
> >
> > > Think this will help, combined with your changes for the Logger?
> >
> > Which changes are you referring to? It should work without any changes.
> >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > --
> > Cheers,
> >
> > Pete
> >
> > *-----------------------------------------------------*
> > | "Faced with the choice between changing one's mind, |
> > | and proving that there is no need to do so - almost |
> > | everyone gets busy on the proof." |
> > | - John Kenneth Galbraith |
> > *-----------------------------------------------------*
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
