Not processed by all BeanPostProcessors
Other URL
Business class cannot be proxied by AOP.
Bean life cycle-the pit of BeanPostProcessor_feiying0canglang's blog -CSDN blog
BeanPostProcessor loading order and its impact on Bean | 知源博客
Introduction
Spring integrates Shiro and reports the following information at startup:
Bean 'userService' of type [com.example.user.service.impl.UserServiceImpl] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
LifecycleBeanPostProcessor
Other URL
Shiro learning the role of LifecycleBeanPostProcessor_hxm_Code's column-CSDNblog
Introduction
There is no need to configure the life cycle processor when configuring shiro. When the shiro framework integrates spring, this matter will not be handed over to the user to do it, and the processor will be injected by itself. Check the ShiroBeanConfiguration in the config package under the shiro-spring jar, it has been injected.