- The importance of AOP
is to seperate secondary / cross cutting concerns (middleware service
implementations - TX, security, logging, session management, state persistence
etc services) from primary / core concerns (business logic implementation).
- AOP recommends to
write one Advice for each service implementation
-The types of Advices
are
i) Method before Advice
- sub class of MethodBeforeAdvice
ii) After Advice - sub
class of AfterReturningAdvice
iii) Around Advice - sub
class of MethodInterceptor (3rd party vendor)
iv) Throws Advice - sub
class of ThrowsAdvice
No comments:
Post a Comment