DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=42664>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=42664 Summary: JUL Appender Product: Log4j Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: Appender AssignedTo: log4j-dev@logging.apache.org ReportedBy: [EMAIL PROTECTED] Hi all, I was thinking of bridging JUL and log4j, so that existing log4j-enabled applications could correctly write to JUL-enabled environments, with the full layout/filter/handler log4j support without code changes, and minimal config changes. At the moment, using the ConsoleAppender works fairly, except that the log4j log levels are not mapped to JUL levels. For example, it is observed under SJSAS9 that all log4j messages show up at the INFO (stdout) or WARNING (stderr) level, regardless of what method (trace/debug/info/etc) the application called. I have created a JulAppender to solve this issue. If you feel it is appropriate, feel free to review it and consider it as a log4j enhancement. Usage is simple: in log4j configuration, replace "org.apache.log4j.ConsoleAppender" with "org.sagimann.log4j.JulAppender". Everything else stays the same: layouts, patterns, etc. Additional documentation is provided in the code at the moment. Awaiting comments... Thanks. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
