If there are special cases, they’d probably be handled differently in each of these strategies. For example, with self-logging exceptions, perhaps certain subclasses (e.g. checked exceptions in package com.foo.xyz) log themselves as warnings. Or one of the constructors allows you to pass in a log level.

In the end, I would look and say if some exception handling should be logged as a warning, should it really be treated as an exception? If so, implement a special strategy. If not, maybe use something else.

One additional disadvantage with AOP exception logging is the ability to add context to the logs. For example, if you wanted to log the state of some class data member when an exception occurred:


public class A {
public int x;


public void createUser(String username) {
try {
doSomething();
} catch(SomeException e) {
LOG.error("some exception when x = " + x, e);
}
}
}


AOP logging is sometimes “one size fits none”.