The join points are opportunities, but all of them are not considered where the aspects can be applied. A pointcut is where the developers decide to apply the aspect to perform a specific action for the cross-cutting concern. The pointcut is written using the method names, class names, and regular expressions to define the matching packages, classes, and methods where aspects can be applied.
- Preface
- Spring at Glance
- Dependency Injection
- The life of a bean
- Loading the configuration
- Object creation
- Setting the bean name
- Setting the bean factory
- Bean post processing with postProcessBeforeInitialization
- Property population
- Initializing the bean
- Bean post processing with postProcessAfterInitialization
- Use the bean
- Destruct the bean
- Case 1: Using custom initialization and destruction methods
- Case 2: Using InitializingBean to provide initialization
- Case 3: Using DisposableBean to provide release of memory
- Case 4: Making the bean aware of the container
- Case 5: Using BeanPostProcessor
- Using JSR-250 annotations for the bean life cycle
- Instance creation
- Dependency injection
- Summary
- The life of a bean
- Accelerate with Spring DAO
- Aspect-Oriented Programming
- Core and cross-cutting concerns
- Aspect-oriented programming
- Part 1 - Creating applications for the core concern (JDBC)
- Part 2 - Integration of Log4j
- Part 3 - Writing logging aspects
- Annotation-based aspects
- Introduction advice
- Summary
- Core and cross-cutting concerns
- Be Consistent - Transaction Management
- Exploring Spring MVC
- Be Assured, Take a Test Drive
- Make It Safe - Security Management
- Explore the Power of RESTful Web Services
- Exchange Information - Use Messaging
- Be Active - Reactive Programming
Pointcut
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.