logging-log4cxx-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Curt Arnold <carn...@apache.org>
Subject Re: XMLSocketAppender
Date Wed, 06 Dec 2006 00:50:20 GMT

On Dec 3, 2006, at 4:28 PM, Marc Rossi wrote:

>
> Went ahead and added the following line to the end of the
> XMLSocketAppender::renderEvent() method:
>
>     os1->write(output)
>
> and it is now sending out the xml event info (although it still isn't
> displaying properly in chainsaw).  Not sure why this line wasn't  
> already
> there (almost the same line was commented out in the original source).
>

Logged and resolved as http://issues.apache.org/jira/browse/ 
LOGCXX-164.  Also logged https://issues.apache.org/jira/browse/ 
LOGCXX-165 as the original 0.9.7 and the current implementation could  
result in corrupted XML due to a mismatch of the expected UTF-8  
encoding and the actual encoding, however fixing that would probably  
warrant a complete review of SocketAppender and XMLSocketAppender in  
log4cxx.

The code using the Microsoft Platform SDK macro T2A was removed  
during the migration to supporting both single char and wide char  
logging simultaneously.  It just wasn't restored when things were put  
back together.



Mime
View raw message