logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41169] - NTEventLogAppender.dll :: "missing" event description
Date Fri, 15 Dec 2006 22:52:12 GMT
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=41169>.
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=41169


carnold@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From carnold@apache.org  2006-12-15 14:52 -------
Committed in rev 487688 in log4j 1.2 branch, 487701 on trunk.

There were several different issues involved.  The NTEventLogAppender.dll did attempt to register
itself 
to provide message resources for the event viewer, however it did not provide an absolute
file path to 
the DLL and used the wrong key types.  If the registry entries had been corrected, the previous
DLL did 
not expose the MESSAGETABLE resource despite it being present in the link step.  Combining
the 
VERSION resource and the MESSAGETABLE resource into a single resource file before linking,
fixed that 
problem.  In addition, the category values used for the event logs were the int values of
the level plus 
one, for example, a INFO message would have a category of 10001, WARN would be 20001, etc.
 This 
would cause the category string lookup to fail since the specs say that categories should
start at 1 and 
be contiguous.

In addition, the log4j 1.2 branch did not have bug 39437 applied which eliminated unnecessary

conversion back to the local code page.

The initial commits on the trunk in rev 487685 were misidentified as being related to bug
39437.

The new DLL's should be compatible with earlier versions of log4j.  When properly registered
(by use, 
doesn't support regsvr32 at this time), existing events should have properly displayed messages,
but 
the categories will still show the integer value of the level + 1.

-- 
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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org


Mime
View raw message