[ http://nagoya.apache.org/jira/browse/RUNTIME-30?page=history ]
Niclas Hedhman resolved RUNTIME-30:
-----------------------------------
Resolution: Won't Fix
Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net
> Logging is done using category names separated by slashes instead of dots
> -------------------------------------------------------------------------
>
> Key: RUNTIME-30
> URL: http://nagoya.apache.org/jira/browse/RUNTIME-30
> Project: Merlin Runtime
> Type: Bug
> Components: LOGGING
> Versions: 3.3.0
> Environment: Merlin 3.3-RC6
> Reporter: Bruno Dumon
> Assignee: Stephen McConnell
>
> 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:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
