Re: [jira] Commented: (LOGCXX-121) LoggingEvent serialization and deserialization is stubbed out

[Andreas Fester <af...@apache.org>]

Curt Arnold (JIRA) wrote:
> [
> http://issues.apache.org/jira/browse/LOGCXX-121?page=comments#action_12377463
> ]
> 
> Curt Arnold commented on LOGCXX-121: ------------------------------------
> 
> One of the reasons that I had this assigned to me is that it tied into one
> of my very long standing TO-DO items in log4j which was to analyze the
> log4j serialization form and then modify log4j 1.3 so that it was
> compatible with log4j 1.2.  If the log4cxx and log4j 1.3 serialized forms
> could be unified with the log4j 1.2 serialized form, then one instance of
> Chainsaw could work with all of them.  If the log4cxx serialized form is
> not compatible with log4j, they having the serialized form is of very
> little value.

Thats exactly my approach. I wanted to have a look into chainsaw for
quite some time and thought this would be a good chance to dig into this
issue.
I just wanted to avoid that we are both working on the same issue and waste
time, so I assigned it to me. If you think you can start working on it
then just tell me, it will still require some days for me to really start
with it :-)

Thanks,

	Andreas

Re: [jira] Commented: (LOGCXX-121) LoggingEvent serialization and deserialization is stubbed out

[Curt Arnold <ca...@apache.org>]

On May 3, 2006, at 8:08 AM, Andreas Fester wrote:
> Thats exactly my approach. I wanted to have a look into chainsaw for
> quite some time and thought this would be a good chance to dig into  
> this
> issue.
> I just wanted to avoid that we are both working on the same issue  
> and waste
> time, so I assigned it to me. If you think you can start working on it
> then just tell me, it will still require some days for me to really  
> start
> with it :-)
>
> Thanks,
>
> 	Andreas
>

If you have the time or interest, please proceed.  You may want to  
review the log4j-dev mailing list and bugzilla searching for  
serialization.  log4j LoggingEvent serialization used default  
serialization (which is discouraged) and changes in the log4j 1.3  
(log4j/trunk) development broke serialization compatibility with the  
might more widely deployed log4j 1.2 (log4j/branches/v1_2-branch).   
The best resolution would be to restore serialization compatibility  
between log4j 1.3 and 1.2 and make log4cxx compatible with 1.2.  The  
log4j unit tests contain some serialization tests that could be  
migrated over to log4cxx.