DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13659>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13659

NTEventLogAppender event categories and usernames not logged

           Summary: NTEventLogAppender event categories and usernames not
                    logged
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Appender
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Categories are showing up as numbers instead of strings in my Windows 2000
event log. Also, username is always displayed as N/A. I've posted a patch
to the log4j-dev list with corrections and a couple of other enhancements
to add to the flexibility of the NTEventLogAppender.

NTEventLogAppender changes in patch:
      - Fixed logging of event categories so the text strings show up in the
        NT Event Log instead of numbers.
      - Added a flag to NTEventLogAppender class and support for it in 
        nteventlog.cpp, that allows the programmer to turn on or off the 
        display for the current username in the NT Event Log. Instead of N/A.
      - Added a way for the programmer to specify their own resource only
        DLL so they can user their own custom event categories, instead of
        the ones compiled into NTEventLogAppender.dll. Very useful since 
        categories were never really intended to convey the level of the log
        messages anyway.
      - Added a new class called CategorizedMessage. It's used a wrapper 
        around an existing log message so a category number can be associated
        with it.
      - Added a way for the programmer to specify their own resource only
        DLL so they can user their own custom event mesage, instead of
        the one compiled into NTEventLogAppender.dll. Not very useful since
        there can still be only one event message and the ID has to be 4096,
        but it was easy and leaves room for future enhancements like supporting
        multiple event messages.

Thanks.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to