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: [jira] [Commented] (LOG4J2-1) Custom rendering of exception associated with logging event
Date Sun, 29 Jan 2012 07:55:08 GMT
I assume this is spam. How do I remove it.

On Jan 28, 2012, at 11:46 PM, bill gate (Commented) (JIRA) wrote:

> 
>    [ https://issues.apache.org/jira/browse/LOG4J2-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195707#comment-13195707
] 
> 
> bill gate commented on LOG4J2-1:
> --------------------------------
> 
> 这个是log4j的2版本么?为啥没有下载链接啊???
> 
>> Custom rendering of exception associated with logging event
>> -----------------------------------------------------------
>> 
>>                Key: LOG4J2-1
>>                URL: https://issues.apache.org/jira/browse/LOG4J2-1
>>            Project: Log4j 2
>>         Issue Type: Improvement
>>         Components: Layouts
>>           Reporter: Curt Arnold
>> 
>> In http://marc.info/?l=log4j-user&m=120898200413495&w=2, Robert Pepersack
essentially asks for a method of overriding the use of Exception.printStackTrace() to capture
the stack trace of the associated exception.  This can partially be done in log4j 1.x by providing
a custom layout that returns false for ignoresThrowable and then performs the rendering of
the exception as part of the layout.  However, it would not affect LoggingEvents that were
deserialized.  Also, if an AsyncAppender is used, the layout would be rendering an exception
after it may have been modified.
>> The log4j 2 pipeline should not have this issue as the extraction phase done by the
layout should pull any info needed from the exception and the responsibility would not be
split among WriterAppender, ThrowableInformation and the layout.  So likely there is no additional
design criteria involved here, just the final design should be checked that it satisfies this
use case.
> 
> --
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
> For more information on JIRA, see: http://www.atlassian.com/software/jira
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message