logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Davies (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-320) Location Information
Date Wed, 11 Jan 2012 03:13:40 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183828#comment-13183828

Adam Davies commented on LOG4NET-320:

I agree it would be much more beneficial to relocate the code.  However, the XMLLayout works
quite differently than any other layout in that it has no converter.  The XMLLayout renders

I can see following possiblity:

Move the code as suggested.
In PatternConverter, create a LocationOffset property and a GetLocationInfoByOffset(LoggingEvent)
In each converter that uses Location Information, call base.GetLocationInfoByOffset() for
the offset location

I will code and test over the next few days.
> Location Information
> --------------------
>                 Key: LOG4NET-320
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-320
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 1.2.11
>            Reporter: Adam Davies
>            Priority: Minor
>              Labels: location, locationoffset, patch, stacktrace
>             Fix For: 1.2 Maintenance Release
>         Attachments: LocationOffset.patch
> Add the ability to offset the stacktrace information.  On occasion there is a need to
skip the first n stack locations.  For example, if using a generic method to log exceptions
and then rethrow them; the generic method is irrelevant information in the stack.

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


View raw message