Types of [SpringAOP] advice:
Before advice: Advice that executes before a join point, but which does not have the ability to prevent execution flow proceeding to the join point (unless it throws an exception).
After returning advice: Advice to be executed after a join point completes normally: for example, if a method returns without throwing an exception.
After throwing advice: Advice to be executed if a method exits by throwing an exception.
After (finally) advice: Advice to be executed regardless of the means by which a join point exits (normal or exceptional return).
Around advice: Advice that surrounds a join point such as a method invocation. This is the most powerful kind of advice. Around advice can perform custom behavior before and after the method invocation. It is also responsible for choosing whether to proceed to the join point or to shortcut the advised method execution by returning its own return value or throwing an exception.
Alder Potenz wrote:What are the real world or common scenario where we need or want to use AOP introduction.
- part of Java's support for generics, which is covered within the collections documentation;
what is <T>?
, yes we all do and the maze seems to be forever growing! Trick is not to worry as nobody can know everything, but after a while you will notice that technology changes the fundamental concepts don't.
i feel like a mouse in a very big java maze
- Close but "no cigar" , as there are other Spring projects to access data like spring data, which (hopefully) is used in the model packages.
Moreover, Spring MVC is only a part of the complex solution, which can take care of many aspects of your application, (such as testing or data access).