Kamal; Thanks for the quick response, but I am not sure how the logging code would look like. I know you are busy like all of us in this great industry, but could you be a little more elaborate in your explanation.
Thanks Rocky -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kamal Ahmed Sent: Tuesday, December 19, 2006 10:38 AM To: Log4J Users List Subject: RE: Messaging Mapping? Rocky, Try using Resource Bundles and messages.properties The mapping is done in messages.properties file Here is a sample: G8dEvent.NullSourceType='source type id' must not be null WmTimedFileAppenderBase.NullDatePattern=DatePattern option is not set for appender {0}, using default: {1} WmLogManager.NullLogDir=Log file directory cannot be null -----Original Message----- From: Martinez, Roque [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 19, 2006 10:31 AM To: log4j-user@logging.apache.org Subject: Messaging Mapping? All; I have been doing some research and I keep coming across a thread in this mailing list which describes how to map messages to a specific text. I notice the implementation requires a number of constructions each time a log message is being created. I am wondering if anyone has been able to create a different methodology to accomplish the same. Example IO100-01 becomes IO100-01 File not found File Name: test.properties Thanks Rocky --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
