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?


Scott Deboy
Principal Engineer
COMOTIV SYSTEMS
111 SW Columbia Street Ste. 950
Portland, OR  97201
Office: 503.224.7496
Direct Line: 503.821.6482
Cell: 503.997.1367
Fax: 503.222.0185
[EMAIL PROTECTED]
www.comotivsystems.com

-----Original Message-----
From: Curt Arnold [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 21, 2007 10:41 AM
To: Log4J Developers List
Subject: Re: apache-log4j-component-1.0 rc2


On Jun 21, 2007, at 1:18 AM, Scott Deboy wrote:

> I'd still like us to consider finishing the property support  
> included in LoggerRepositoryEx (mostly requiring new functionality  
> being added to LoggingEvent).  It would make finishing up the  
> backporting of the appenders & receivers essentially complete.
>

Forgot about that over my Oregon vacation.  I don't see a way to do  
it in component and I'm hesitant to add what appeared to be a  
complicated feature (at least how it was implemented in log4j 1.3) to  
log4j 1.2.


> Also, I'm not sure of the state of our support for slf4j via  
> ULogger - are we planning on removing that or tracking slf4j?
>

Though the heritage of org.apache.log4j.ULogger is tied up with UGLI  
and SLF4J, its presence in component is strictly to support log4j 1.3  
backports that used LoggerRepositoryEx.getLogger() for internal  
logging.  I would not anticipate either removing it or tracking  
slf4j.  All this component stuff is there to support backports and  
will not be brought over to log4j 2.0.





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to