sécurité de printemps pas admissible à l'auto-proxying

Question

peut-on élaborer ce que ces informations signifie lors de la demande de démarrage?

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 

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

Answer 1

Ceci est un message assez normal. Un BeanPostProcessor est une construction Spring pour modifier/enrubanner/envoyer par proxy des beans dans le contexte. En raison de la façon dont le cycle de vie du contexte fonctionne, certaines choses doivent être configurées avant le BeanPostProcessor jeter un coup d'oeil, ce qui conduit à ce message.

Ce n'est presque jamais un problème, d'où le niveau INFO. Les composants qui déclenchent le message sont généralement les composants internes de Spring.