On Dec 1, 2005, at 8:02 AM, George Sebastian wrote:
Hi
I have a requirement for the detailed logging of an application.
...
I need each module is some what big (but runs in a single process)
so I like
to have some common naming (like component name) for a log request
so that i
can easily identify from which module the request came from.
Maybe you are getting at something else, but that appears to be
exactly what the logger name is designed to do. There may be some
confusion since a class name is often used as a logger name, but you
are completely free to use a different strategy. The logger name
should be thought of as a "topic" of logging messages and it is up to
you to design a set of topics that make sense for your application.
Like extending LoggingEvent to put my own custom event or so
There is nothing but pain down that path.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
