Albert Zhou wrote:
>Steve,
>
>It appears that the target attribute of the logging
>element got ignored. That is, no matter what value is
>specified, it always logged to the default target, ie,
>the console by default(?), or whatever file if a
>target element with name="default" is included within
>the logging element. A bug?
>
It's a bug - and its now fixed.
The following directive will result in logging to a file:
<logging priority="INFO" target="kernel">
<category name="logging" priority="WARN" />
<target name="kernel">
<file location="kernel.log" />
</target>
</logging>
>
>Is the name attribute of the logging element useful at
>all? Useful if running merlin within another
>container?
>
>
Yes and no - the name attribute (on the <type><loggers><log
name="xxx"/> ... ) ensures that a logging category will be created for
the named category. This can be used to validate logging directives
contained within a <component/> declaration (although validation of this
aspect is not implemented at this time).
>Is it possible to specify more than one target for any
>category, eg, one to the default console and one to a
>file? How? I had an impression that logkit supports
>mutiple targets.
>
>
Its not currently possible. Basically, the DefaultLoggerManager isn't
even wrapped in an interface - the reason for this is are the following
(a) I wanted to get a good idea of the actual exposure we need for the
logging manager, and (b) I wanted to get a good picture on what was
actually needed over and above excalibur/logging/LogManager. The main
concern I have is that the <categories> and container <category>
elements that are defined as part of Merlin 2 should really be defined
as part of excalibur/logger and imported into the meta-data layer. With
that in mind, the current implementation focussed on what was needed to
get a better understanding of the implications and as such it does not
address all of excalibur/logger functionlity. I second issue was
related to the structure of the excalibur/logger XML that does not lend
itself to the seperation of directives across different Merlin units
such as the kernel, containers and components.
Cheers, Steve.
>Thanks as always.
>
>Cheers,
>Albert
>
>=====
>Regards,
>Albert
>
>
>--
>
>Stephen J. McConnell
>
>OSM SARL
>digital products for a global economy
>mailto:[EMAIL PROTECTED]
>http://www.osm.net
>
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
