Thanks for the feedback. Hope you don't mind me copying it to log4j-
dev.
The regsvr32 behavior is expected. It would be an nice enhancement
of NTEventLogAppender.dll to add the DllRegisterServer entry point
and let regsvr32 force the registration of the DLL (which would avoid
the manual removal of any old registration). The existing code
checks for the key when an event is logged and only sets the values
if the key is missing (which is the reason the key needs to be
manually deleted). I'll see what it would take to add that code.
On Feb 28, 2007, at 11:00 AM, CHANG Shuh wrote:
Hi Curt,
I'd vote YES for log4j 1.2.15 release after I took it out for a
spin but
only tested for the NTEventLogAppender.dll and Syslog's new header
property.
The latest NTEventLogAppender.dll shows a very clean event logging. I
just copied the DLL to the C:\WINDOWS\system32 folder, reomved the old
registry, restarted my web app, and triggered some events for the log.
Everything works as advertised. There is a minor thing though. If I
use
the regsvr32 command to manually register the
C:\WINDOWS\system32\NTEventLogAppender.dll file, it still gives me
that
message: "c:\windows\system32\NTEventLogAppender.dll was loaded,
but the
DllRegisterServer entry point was not found. The file an not be
registered." I guess that the NTEventLogAppender.dll is not meant for
regsvr32 or something else. Anyway, it works by just copying the
DLL to
the C:\windows\system32 folder, and that's what it matters.
As for the Syslog, with the new "header" property turned on, the
log in
Syslog on a Linux platform looks a lot better than before. It's more
consistent with the other logging format recorded by the file
appenders.
Great fixes. Thanks for the great job.
Regards,
Shuh
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
