[logback-dev] [JIRA] Commented: (LBCLASSIC-303) LoggingEvent.getCallerData() fails when called from a sub class
Ceki Gulcu (JIRA)
noreply-jira at qos.ch
Tue Nov 1 23:22:12 CET 2011
[ http://jira.qos.ch/browse/LBCLASSIC-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12246#action_12246 ]
Ceki Gulcu commented on LBCLASSIC-303:
--------------------------------------
I believe that writing "new LoggingEvent(this.getClass().getName()" biases the whole test.
> LoggingEvent.getCallerData() fails when called from a sub class
> ---------------------------------------------------------------
>
> Key: LBCLASSIC-303
> URL: http://jira.qos.ch/browse/LBCLASSIC-303
> Project: logback-classic
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Greg Thomas
> Assignee: Logback dev list
>
> This is probably best demonstrated with a code example;
> package com.example;
> import ch.qos.logback.classic.Level;
> import ch.qos.logback.classic.Logger;
> import ch.qos.logback.classic.LoggerContext;
> import ch.qos.logback.classic.spi.LoggingEvent;
> public class Test {
> Logger logger;
> public static void main(String[] args) {
> Test test = new Test();
> test.go();
> }
> private void go() {
> SuperClass anotherClass = new SuperClass();
> anotherClass.go();
> anotherClass = new SubClass();
> anotherClass.go();
> }
> private class SuperClass {
> public void go() {
> LoggerContext lc = new LoggerContext();
> lc.setName("default");
> // ... a logger
> logger = lc.getLogger("root");
> LoggingEvent le = new LoggingEvent(this.getClass().getName(),
> logger, Level.DEBUG, "Test logging event", new Exception(
> "test Ex"), new String[] { "something" });
> StackTraceElement[] callerData = le.getCallerData();
> System.out.println("LoggingEvent in " + this.getClass().getName() + " has "
> + callerData.length + " stack trace elements:");
> for (StackTraceElement stackTraceElement : callerData) {
> System.out.println("Element=" + stackTraceElement);
> }
> }
> }
> private class SubClass extends SuperClass {
> }
> }
> The output of this is as follows;
> LoggingEvent in com.example.Test$SuperClass has 2 stack trace elements:
> Element=com.example.Test.go(Test.java:20)
> Element=com.example.Test.main(Test.java:14)
> LoggingEvent in com.example.Test$SubClass has 0 stack trace elements:
> This is despite exactly the same go() method being called; it's not being modified in the subclass. Note that although the example uses inner classes, the same behaviour is exhibited in regular classes too.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the logback-dev
mailing list