posted 15 years ago
I guess it depends on what is the purpose of your log.
Using AOP based logging usually useful for tracing method calls, because most AOP implementations allow pre/post/around advice. Since you usually only have access to the method and its parameter/return value only..that's all the information you can log.
With standalone logging framework like log4j, it is more flexible for where/when/what to log, but it makes your code base verbose and cluttered. Let's face it, most of the time log4j is used more for runtime/production debugging support..where it print out verbose process and state information.
It goes back to what is your goal and design it appropriately.