On Jun 21, 2007, at 12:56 PM, Scott Deboy wrote:
I'd like to finish implementing repository-wide property support - I
think what would solve both issues is to have
LoggingEvent.getProperties
just return the repository properties, not the MDC properties.
LoggingEvent.getMDC would continue to return only MDC-defined
properties.
That's enough to meet my current needs and doesn't complicate
LoggingEvent or affect backward-compatibility.
Thoughts?
I think I might have a way to do it in component. Chainsaw sets the
repository selector in the start up, so it should be possible to
create a HierarchyEx class that derives from Hierarchy, implements
LoggerRepositoryEx and overrides getLogger() and other methods
sufficiently to get repository properties into the logging event.
LoggerRepositoryExImpl is still useful when an backported appender
needs to expose LoggerRepositoryEx on an existing logger repository
that it has no control over.
It would be a bit more complicated to add it in component instead of
directly implementing it in log4j 1.2, but I'd feel more comfortable
not tweaking a fairly significant code pathway.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
