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=32618>. 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=32618 ------- Additional Comments From [EMAIL PROTECTED] 2004-12-09 23:49 ------- A.2. Globalization. For the enterprise logging we need globalized messages (translated) for message level logging API's: info, warn, error, fatal. The remaining logging API's are considered trace level logging API's, and do not require message translation. - For message level logging, support globalized variants on the new EnterpriseLog interface: info(Class callingClass, String methodName, String messageID); info(Class callingClass, String methodName, String messageID, Object messageParam); info(Class callingClass, String methodName, String messageID, Object[] messageParams); same for warn, error, fatal. - Utility function to support formatting for other purposes (exception strings): formatMessage(String messageID); formatMessage(String messageID, Object messageParam); formatMessage(String messageID, Object[] messageParams); Ensure that component has an assurance that the message will be translated/formatted as expected: - ALL message translation must be done using the standard java.util.ResourceBundle class, or functional equivalent. - ALL message formatting must be done using the standard java.text.MessageFormat class, or functional equivalent. - Bind a ResourceBundleName to an EnterpriseLog instance. - Expects that the named ResourceBundle is available to the logger. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
