spring security不符合自动代理条件

Question

任何人都可以详细说明这些信息在启动应用程序时的含义

INFO: Bean 'org.springframework.aop.aspectj.AspectJPointcutAdvisor#0' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
Jan 13, 2010 11:00:34 AM org.springframework.context.support.AbstractApplicationContext$BeanPostProcessorChecker postProcessAfterInitialization
INFO: Bean '(inner bean)#2' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
Jan 13, 2010 11:00:34 AM org.springframework.context.support.AbstractApplicationContext$BeanPostProcessorChecker postProcessAfterInitialization
INFO: Bean 'org.springframework.aop.aspectj.AspectJPointcutAdvisor#1' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
Jan 13, 2010 11:00:34 AM org.springframework.context.support.AbstractApplicationContext$BeanPostProcessorChecker postProcessAfterInitialization
INFO: Bean '(inner bean)#4' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
Jan 13, 2010 11:00:34 AM org.springframework.context.support.AbstractApplicationContext$BeanPostProcessorChecker postProcessAfterInitialization
INFO: Bean 'org.springframework.aop.aspectj.AspectJPointcutAdvisor#2' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
Jan 13, 2010 11:00:34 AM org.springframework.context.support.AbstractApplicationContext$BeanPostProcessorChecker postProcessAfterInitialization
INFO: Bean '(inner bean)#6' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
Jan 13, 2010 11:00:34 AM org.springframework.context.support.AbstractApplicationContext$BeanPostProcessorChecker postProcessAfterInitialization
INFO: Bean 'org

参考:http://bamboo.ci.codehaus.org/build/viewBuildLog.action; jsessionid= 85C63FD38CA3A5320AE8CECE84D570B8?buildNumber=3& buildKey= MODFORJ-RASASBREAKFAST

Answer 1

这是一个相当正常的消息.A BeanPostProcessor是一个Spring构造,用于在上下文中更改/包装/代理bean.因为上下文的生命周期的工作方式,有些事情必须被配置之前在BeanPostProcessor得到一看,这导致了该消息.

几乎没有什么可担心的,因此INFO水平.触发消息的组件通常是Spring自己的内部组件.