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 31155] New: - Refactor resource bundle access
Date Thu, 09 Sep 2004 23:12:11 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=31155>.
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=31155

Refactor resource bundle access

           Summary: Refactor resource bundle access
           Product: Log4j
           Version: 1.3alpha
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Other
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: ggregory@seagullsw.com


I need to throw an exception with the same message I am logging. The localized
l7d  methods already perform the resource lookup and builds the message based on
Object parameters; I would rather not have to do it again in my code. I
therefore propose the attached patch to Category.java version 1.88.

The main point of this patch is to refactor the parameterized l7d method and
extract out the code that builds a message based on a key and Object array.

The patch also contains Javadoc fixes.

Thank you for considering this request and patch.

---------------------------------------------------------------------
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