When searching for errors, I really like to see the whole stacktrace, so I am really glad that every exception has it's cause and is not masking the real error cause. Genman's idea isn't so bad and I think it shouldn't be too difficult to write your own ConsoleAppender (at first glance ;-) Just inherit from the log4j ConsoleAppender, overwrite append(LoggingEvent), do you own thing when there is a throwableInfo or let the superclass do everything if not.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3860568#3860568 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3860568 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
