logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <ralph.go...@dslextreme.com>
Subject Re: core.impl.Log4jLogEvent.LogEventProxy
Date Mon, 31 Mar 2014 06:36:41 GMT
Out of curiosity, why does implementing an XML socket server require touching the LogEvent?
 What are XMLLogEventInput and JSONLogEventInput going to do that would require that?

Ralph

On Mar 30, 2014, at 8:04 PM, Gary Gregory <garydgregory@gmail.com> wrote:

> As I am working on LOG4J2-583 I ran into core.impl.Log4jLogEvent.LogEventProxy.
> 
> - LogEventProxy is used to move events across threads internally
> - A real Log4jLogEvent is used in the SerializedLayout.
> 
> Why the different?
> 
> As you answer, if you can avoid committing to Log4jLogEvent that would be great as I
currently have pending changes there related to LOG4J2-583.
> 
> I am wondering if SerializedLayout should use LogEventProxy or if LogEventProxy is a
leftover from old development.
> 
> Thank you,
> Gary
> -- 
> E-Mail: garydgregory@gmail.com | ggregory@apache.org 
> Java Persistence with Hibernate, Second Edition
> JUnit in Action, Second Edition
> Spring Batch in Action
> Blog: http://garygregory.wordpress.com 
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory


Mime
View raw message