avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Created: (RUNTIME-30) Logging is done using category names separated by slashes instead of dots
Date Fri, 28 May 2004 12:00:01 GMT

  A new issue has been created in JIRA.

View the issue:

Here is an overview of the issue:
        Key: RUNTIME-30
    Summary: Logging is done using category names separated by slashes instead of dots
       Type: Bug

     Status: Open
   Priority: Major

    Project: Merlin Runtime Platform

   Assignee: Stephen McConnell
   Reporter: Bruno Dumon

    Created: Fri, 28 May 2004 4:59 AM
    Updated: Fri, 28 May 2004 4:59 AM
Environment: Merlin 3.3-RC6

When trying to configure the Merlin logging (using log4j, but I guess the problem is the same
with logkit), I stumbled across the following problem:

the name of the logging category used when requesting a logger from the logging subsystem
is specified as eg "/a/b" instead of "a.b", which is unrecognized by log4j. iow, log4j thinks
this is a category named "/a/b" instead of a category hierarchy consisting of a logger called
"a" with a sublogger called "b".

As a possible solution, it could be considered to let the logger category be specified explicitely
on the component deployment specification, instead of automatically taking the container and
component names for this. This is for example what ECM did:

<component-instance name="something" logger="something.thisorthat" ... />

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org

View raw message