Consistent Environment access in XML bean definition parsing code [SPR-12248]

[spring-projects-issues]

Juergen Hoeller opened SPR-12248 and commented

Dating back to the Spring 3.1 days, there is quite a bit of explicit passing around of Environment references in Spring's XML bean definition parsing code, e.g. in BeanDefinitionParserDelegate and DefaultBeanDefinitionDocumentReader. With the introduction of a convenient XmlReaderContext.getEnvironment() method, there is really no need for explicit Environment fields anymore.

This allows for deprecating BeanDefinitionDocumentReader.setEnvironment and BeanDefinitionParserDelegate(XmlReaderContext, Environment), as well as as undeprecating BeanDefinitionParserDelegate(XmlReaderContext). Some preparation measures are also going to be backported to 4.0.8 and 3.2.12, including a fully working version of the latter constructor.

---

Affects: 4.1 GA

Issue Links:

• make context:exclude-filter expression supports placeholder like context:component-scan base-package [SPR-10424] #15057 make context:exclude-filter expression supports placeholder like context:component-scan base-package
• please let context:component-scan base-package eval placeholder then split by comma [SPR-10425] #15058 please let context:component-scan base-package eval placeholder then split by comma

Referenced from: commits de3ea5d, 5ecdd8c, d46c3fc