I'm reading up on Spring at the moment and one of the examples used for a use of AOP is logging the start and end of method calls.
I've also read that using AOP can impact performance.
Is using Spring AOP a good idea for this type of logging? My understanding is that Spring uses Dynamic AOP would it be be better to use Static AOP (Like AspectJ) for this type of AOP.
Curently the coding policy of the company I work for requires a ridiculous amount of logging and i want to reduce the ammount of logging code I have to write and improve the readability of my code.
Am I barking up the wrong tree?
Read this blog-post about your performance concerns.
The way to think of AOP is to put the provided functional benefits in the first place. If automated logging is your requirement and AOP fits it - go for it.
That said, load-time weaving is, of course, preferred if fine-grained logging is required.