Allowing the MethodLocationPatternConverter to skip certain methods from the
call stack when trying to log the caller method (Solution for Log4Net wrappers)
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: LOG4NET-306
URL: https://issues.apache.org/jira/browse/LOG4NET-306
Project: Log4net
Issue Type: Improvement
Components: Other
Affects Versions: 1.2.10, 1.2.9
Reporter: Jon Abaunza
Priority: Blocker
There are several environments where it is required to develop a wrapper around
Log4Net for backward compatibility with previous logging systems.
The problem comes when it is required to obtain the method name. The system
goes up in the StackTrace and identifies the wrapper method as the first user
method and therefore logs the name of the wrapper instead of the real caller
method.
The solution would be as simple as creating a new MethodAtribute (lets say
log4Net.SkipMethodForMethodLocation). I would be able to decorate my method
with it and the MethodLocationPatternConverter would continue looking up in the
stackTrace for the next user method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
