RE: Logging configuration

Ok, thanks, Steve! That works nicely. :-)

Not quite sure I understand the "categories" mechanism, though... Is there a
page somewhere that explains this?


Also, is it possible to output "info" and above to the console, and "debug"
and above to a file?

If so, how?

Thanks!



> -----Original Message-----
> From: Stephen McConnell [mailto:[email protected]]
> Sent: July 25, 2004 23:14
> To: 'Avalon framework users'; [email protected]
> Subject: RE: Logging configuration
>
>
>
>
> > -----Original Message-----
> > From: David Leangen [mailto:[email protected]]
> > Sent: Sunday, July 25, 2004 15:56
> > To: [email protected]
> > Subject: Logging configuration
> > Importance: High
> >
> >
> > I'd like to configure my components to log to a file.
> >
> > I read this page:
> >
> http://avalon.apache.org/products/runtime/system/logging/api/index.html
> >
> >
> > But it doesn't say WHERE or HOW to do this. Doesn't say either what
> the
> > attributes should be.
> >
> > I tried using this tag in a few places:
> >    @avalon.logging.configuration name="someUrl"
> >
> > But that didn't do the trick.
> >
> >
> > Any suggestions?
>
> Merlin looks for the property merlin.logging.config to determine the
> location of the logging configuration.  If you use the -info flag when
> starting merlin you will see the following line:
>
>   ${merlin.logging.config} == null
>
> You can change this value by adding the merlin.logging.config property
> in a property file named merlin.properties.
>
> E.g. in ${merlin.home}/merlin.properties.
>
> The value to assign should be a url pointing to a logging configuration.
> For example:
>
> merlin.logging.config = file:///${merlin.dir}/logging.xml
>
> The contents of the logging.xml file should be something along the lines
> of the configuration file show in this example:
>
> http://avalon.apache.org/products/runtime/system/logging/logkit/examples
> /logkit.html
>
> Hope that helps.
>
> Cheers, Steve.
>
>
> >
> > Thanks!
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
>
>