This is the place! If you don't mind creating a bugzilla issue and attaching the appender, it would help us review it (and find it later)
Here's the bugzilla link: http://issues.apache.org/bugzilla/enter_bug.cgi?product=Log4j If you don't want to go through that, you could attach to this mailing list (but adding to bugzilla gives the highest likelihood it will be reviewed). Scott Deboy COMOTIV SYSTEMS 111 SW Columbia Street Ste. 950 Portland, OR 97201 Telephone: 503.224.7496 Cell: 503.997.1367 Fax: 503.222.0185 [EMAIL PROTECTED] www.comotivsystems.com -----Original Message----- From: Sagi Mann [mailto:[EMAIL PROTECTED] Sent: Thu 6/14/2007 6:52 AM To: log4j-dev Subject: JUL appender Hi all, I'm new to this devlist. I've sent this email once before, but due to some email issues I realize it did not come through. 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. At the moment, using the ConsoleAppender works ok, however, the log4j log levels are not mapped to JUL levels. For example, under Sun AppSrv 9.01, all log4j messages show up at the INFO (stdout) or WARNING (stderr) level, regardless of what method the application called. Anyway, I have created a JulAppender to solve this issue and I was wondering if this is the place to offer it to some sort of review or as a log4j addition; If so, what is the next step? thanks, - s
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
