Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

IN PROGRESS - issue SPR-6779: imported @Configuration classes do not get enhanced and fail to satisfy scoping requirements

Browse Source 
All tests in ImportedConfigurationClassEnhancementTests now pass.  The fix was simple - imported @Configuration class bean definitions were not getting marked with the attribute that indicates that they are indeed @Configuration class bean definitions.  To make this happen, ConfigurationClassPostProcessor's protected checkConfigurationClassCandidate(beanDef) method is being called from within ConfigurationClassBeanDefinitionReader when imported @Configuration classes are being processed.  This is quick and dirty, and the subsequent check-in will refactor the solution appropriately.
This commit is contained in:
Chris Beams
2010-01-29 20:55:03 +00:00
parent 5fdee47841
commit 110b032ad9
4 changed files with 13 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
org.springframework.context/src/test/resources/log4j.xml
View File

@@ -11,7 +11,7 @@
</layout>
</appender>
<logger name="org.springframework.mapping">
<logger name="org.springframework.context">
<level value="debug" />
</logger>