1

I have been looking over these three sites on how to create a map lookup (or any other lookup for that matter) using log4j2:

I understand the general idea behind what I am reading, I am just having a difficult time putting all the bits and pieces together.

Goal

To be able to place a variable, of some sort, in a log4j2.xml file that at configuration time, or runtime, replaces that variable with the values in a resource bundle. This is what i have so far:

Configuration File

enter image description here

Lookup Class

enter image description here

The getValue(key) method looks in a resource bundle for the email values associated with that key.The @Plugin name is "map" which, if i have read correctly, is related to prefixes in the .xml file that are also "map". So, wouldn't "error.notification.emails" get passed into the lookup(String key) method in the MapPropertiesLookup class? What do i need to do in order to get this to work?

j will
  • 3,747
  • 11
  • 41
  • 64

2 Answers2

3

Yes, map is the name of the lookup you are creating. Since Log4j already has a Lookup named map creating another is going to cause problems.

Yes, error.notification.emails should be passed as the key value to the Lookup. Assuming that getValue(key) works your lookup would probably work if it was named something else.

However, it might make more sense for you to file a Jira and ask for a ResourceBundleLookup where the syntax could be something like: ${bundle:bundleName:key}. Of course, "bundleName:key" would be passed to the lookup as the key and it would split the key into the component parts.

If you have further problems you might consider asking on the Log4j developers mailing list.

rgoers
  • 8,696
  • 1
  • 22
  • 24
  • i did what you suggested by creating a different plugin name for my lookup class, but my lookup class doesn't seem to be hitting the breakpoints. I still am getting an exception saying, "Local address contains illegal character in string ``${bundlemap:error.notification.emails}''". In the SMTP appender, the to key is assigned "${bundlemap:error.notification.emails}" and the plugin name is the same. – j will Oct 09 '13 at 18:54
  • I've tried emailing the log4j dev mailing list, but I keep getting error emails in response. – j will Oct 09 '13 at 19:33
3

I added a new lookup for the next release (whether it is a beta or release candidate):

Committed revision 1531064.

You can use it now if you build Log4J from source. The format is documented if you build the site, it is used as follows:

${bundle:BundleName:BundleKey}

For example:

${bundle:com.domain.Messages:MyKey}

The java.util.ResourceBundle class will look for com/domain/Messages.properties on the classpath.

Our JIRA issue: https://issues.apache.org/jira/browse/LOG4J2-420

Gary Gregory
  • 439
  • 5
  • 7