- 13 5月, 2011 7 次提交
-
-
由 Rossen Stoyanchev 提交于
SPR-8289 Ensure BeanNameUrlHandlerMapping and default HandlerAdapters are never 'turned off' through the MVC namespaces
-
由 Costin Leau 提交于
+ fix small doc typo
-
由 Costin Leau 提交于
+ remove duplicate class
-
由 Arjen Poutsma 提交于
-
由 Chris Beams 提交于
@Autowired, @Value and other annotations cannot be applied within Spring Bean(Factory)PostProcessor types, because they themselves are processed using BeanPostProcessors. Javadoc and reference docs have been updated to reflect. Issue: SPR-4935, SPR-8213
-
由 Chris Beams 提交于
Issue: SPR-8327
-
由 Andy Clement 提交于
-
- 12 5月, 2011 8 次提交
-
-
由 Rossen Stoyanchev 提交于
Add method to allow further validation of request mapping infos at startup + other minor javadoc updates.
-
由 Chris Beams 提交于
A subtle issue existed with the way we relied on isCurrentlyInCreation to determine whether a @Bean method is being called by the container or by user code. This worked in most cases, but in the particular scenario laid out by SPR-8080, this approach was no longer sufficient. This change introduces a ThreadLocal that contains the factory method currently being invoked by the container, such that enhanced @Bean methods can check against it to see if they are being called by the container or not. If so, that is the cue that the user-defined @Bean method implementation should be invoked in order to actually create the bean for the first time. If not, then the cached instance of the already-created bean should be looked up and returned. See ConfigurationClassPostConstructAndAutowiringTests for reproduction cases and more detail. Issue: SPR-8080
-
由 Chris Beams 提交于
If the enclosing environment does not implement ConfigurableEnvironment, then @PropertySource annotations are ignored because there is no way to add them to the Environment. Now checking first to see if there are any @PropertySource annotations present before issuing the warning. Issue: SPR-8314
-
由 Arjen Poutsma 提交于
-
由 Andy Clement 提交于
-
由 Andy Clement 提交于
-
由 Sam Brannen 提交于
-
由 Rossen Stoyanchev 提交于
Rename EnableMvcConfiguration->EnableWebMvc, refine method names in WebMvcConfigurer, fix issue with MappedInterceptors
-
- 11 5月, 2011 8 次提交
-
-
由 Chris Beams 提交于
Allows a convenient mechanism for contributing a PropertySource to the enclosing Spring Environment. See @PropertySource Javadoc for complete details and PropertySourceAnnotationTests for examples. Issue: SPR-8314
-
由 Chris Beams 提交于
Allows convenient creation of a Properties-based PropertySource from a Spring Resource object or resource location string such as "classpath:com/myco/app.properties" or "file:/path/to/file.properties" Issue: SPR-8328
-
由 Arjen Poutsma 提交于
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
Users may now call #setRequiredProperties(String...) against the Environment (via its ConfigurablePropertyResolver interface) in order to indicate which properties must be present. Environment#validateRequiredProperties() is invoked by AbstractApplicationContext during the refresh() lifecycle to perform the actual check and a MissingRequiredPropertiesException is thrown if the precondition is not satisfied. Issue: SPR-8323
-
由 Chris Beams 提交于
Issue: SPR-8322
-
由 Chris Beams 提交于
Issue: SPR-8322
-
由 Chris Beams 提交于
Add note that nested @Configuration classes must be static.
-
- 10 5月, 2011 4 次提交
-
-
由 Chris Beams 提交于
Declaring @Bean methods as 'static' is now permitted, whereas previously it raised an exception at @Configuration class validation time. A static @Bean method can be called by the container without requiring the instantiation of its declaring @Configuration class. This is particularly useful when dealing with BeanFactoryPostProcessor beans, as they can interfere with the standard post-processing lifecycle necessary to handle @Autowired, @Inject, @Value, @PostConstruct and other annotations. static @Bean methods cannot recieve CGLIB enhancement for scoping and AOP concerns. This is acceptable in BFPP cases as they rarely if ever need it, and should not in typical cases ever be called by another @Bean method. Once invoked by the container, the resulting bean will be cached as usual, but multiple invocations of the static @Bean method will result in creation of multiple instances of the bean. static @Bean methods may not, for obvious reasons, refer to normal instance @Bean methods, but again this is not likely a concern for BFPP types. In the rare case that they do need a bean reference, parameter injection into the static @Bean method is technically an option, but should be avoided as it will potentially cause premature instantiation of more beans that the user may have intended. Note particularly that a WARN-level log message is now issued for any non-static @Bean method with a return type assignable to BFPP. This serves as a strong recommendation to users that they always mark BFPP @Bean methods as static. See @Bean Javadoc for complete details. Issue: SPR-8257, SPR-8269
-
由 Chris Beams 提交于
-
由 Arjen Poutsma 提交于
-
由 Costin Leau 提交于
+ doc updates
-
- 09 5月, 2011 2 次提交
-
-
由 Arjen Poutsma 提交于
-
由 Rossen Stoyanchev 提交于
-
- 08 5月, 2011 2 次提交
-
-
由 Chris Beams 提交于
Prior to this change, @ComponentScan annotations were only processed at the first level of depth. Now, the set of bean definitions resulting from each declaration of @ComponentScan is checked for configuration classes that declare @ComponentScan, and recursion is performed as necessary. Cycles between @ComponentScan declarations are detected as well. See CircularComponentScanException. Issue: SPR-8307
-
由 Chris Beams 提交于
-
- 07 5月, 2011 9 次提交
-
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
Mirroring the MvcConfigurer#addCustomReturnValueHandlers callback which allows for providing a list of HandlerMethodReturnValueHandler types
-
由 Chris Beams 提交于
Remove 'Method' from RequestMappingHandlerMethodMapping and RequestMappingHandlerMethodAdapter
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
Introduce @EnableAsync#order AsyncAnnotationBeanPostProcessor's 'order' property is now mutable; @EnableAsync's 'order()' attribute allows for setting it, but must have a default value, thus uses the new Ordered#NOT_ORDERED constant - a reserved negative number very unlikely to be otherwise used that may be interpreted as 'not ordered', useful in annotation defaulting scenarios where null is not an option. Introduce first working cut of AsyncConfiguration Remove AsyncCapability
-