- 08 6月, 2013 1 次提交
-
-
由 Sam Brannen 提交于
-
- 05 6月, 2013 3 次提交
-
-
由 Phillip Webb 提交于
Defer @Conditional processing on @Configuration classes until the bean definitions are loaded, rather than when the @Configuration class is parsed. This provides better support for @Conditional implementations that inspect bean definitions. This commit also fixes some minor problems with original implementation and replaces the ConditionalAnnotationHelper class with ConditionEvaluator. Issue: SPR-10534
-
由 Phillip Webb 提交于
Update ConfigurationClassUtils to only consider beans with @Bean methods as 'lite' configuration candidates. Prior to this commit all @Component beans were considered 'lite' configuration candidates which could result in a large number of ConfigurationClass instance being created that would ultimately be ignored. Issue: SPR-10609
-
由 Phillip Webb 提交于
Update AnnotationBeanNameGenerator to only use the value attribute of a @Component meta-annotated annotation when it is a String. Issue: SPR-10580
-
- 04 6月, 2013 1 次提交
-
-
由 Phillip Webb 提交于
Add support for the EnvironmentAware interface with ImportSelector and ImportBeanDefinitionRegistrar implementations. Issue: SPR-10602
-
- 31 5月, 2013 1 次提交
-
-
由 Carson McDonald 提交于
- cherry-pick of pull request #257, which originally applied to 3.2.x
-
- 16 5月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-10568
-
- 15 5月, 2013 3 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-10546 (cherry picked from commit 6e4317eb)
-
由 Juergen Hoeller 提交于
Issue: SPR-10556
-
- 14 5月, 2013 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-10559
-
由 Rob Winch 提交于
Issue: SPR-10130
-
- 10 5月, 2013 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-10307
-
由 Phillip Webb 提交于
Refactor ConfigurationClassEnhancer so that BeanFactory instances are not held against CGLIB Callback objects. Enhanced @Configuration classes now use the BeanFactoryAware interface in order to obtain a BeanFactory. This change has the additional benefit that a static final field can now be used to hold all Callback instances. Issue: SPR-10307
-
- 09 5月, 2013 3 次提交
-
-
由 Phillip Webb 提交于
Add DeferredImportSelector interface that can be used to select imports after all @Configuration beans have been processed.
-
由 Phillip Webb 提交于
Introduce new @Conditional annotation that can be used to filter which @Configuration classes or methods are loaded. @Conditional can be used directly or as a meta-annotation. Condition implementations are provided via the 'Condition' interface and are free to filter based on any criteria available at the time that they run. The ConditionalContext provides access to the BeanDefinitionRegistry, Environment and ConfigurableListableBeanFactory along with a ResourceLoader and ClassLoader. The existing @Profile annotation has been refactored as a @Conditional with the added benefit that it can now be used as a method level annotation.
-
由 Phillip Webb 提交于
Add PropertySourcesPlaceholderConfigurer.getAppliedPropertySources() to allow access to the PropertySources that were actually applied. Issue: SPR-10545
-
- 08 5月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-8108
-
- 07 5月, 2013 4 次提交
-
-
由 Phillip Webb 提交于
Allow classes that are annotated with @Import to be considered as 'lite' @Configuration candidates. Allows the AnnotationConfigApplicationContext to directly register @Import beans even if they are not @Components. Issue: SPR-10533
-
由 Phillip Webb 提交于
Exclude self @Component when parsing @ComponentScan annotations. Issue: SPR-10531
-
由 Phillip Webb 提交于
Implementations of Spring's ImportSelector interface may now implement any of the following *Aware interfaces and have their respective methods called prior to #registerBeanDefinitions: - BeanFactoryAware - BeanClassLoaderAware - ResourceLoaderAware Issue: SPR-10530
-
由 Phillip Webb 提交于
Add AnnotationConfigApplicationContext constructor allow use of a custom DefaultListableBeanFactory. Issue: SPR-10529
-
- 03 5月, 2013 2 次提交
-
-
由 Juergen Hoeller 提交于
This allows for restoring a static MessageSourceResourceBundleLocator implementation, just implementing the interface at the new spi location introduced in HV 4.3 and preserved in 5.0. Issue: SPR-8199
-
由 Juergen Hoeller 提交于
-
- 02 5月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 23 4月, 2013 4 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-9644
-
由 Juergen Hoeller 提交于
This is largely derived from our existing Joda-Time support, with corresponding classes wherever possible. Issue: SPR-9641
-
由 Juergen Hoeller 提交于
Issue: SPR-9641
-
由 Juergen Hoeller 提交于
In particular, avoid accidental usage of ASM for core JDK types - which will fail in case of a new bytecode version in the JDK, even if the application itself has been compiled with an earlier bytecode target. Issue: SPR-10292
-
- 29 3月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
MethodValidationInterceptor autodetects Bean Validation 1.1's ExecutableValidator API now and uses it in favor of Hibernate Validator 4.2's native variant. SpringConstraintValidatorFactory implements Bean Validation 1.1 "releaseInstance" method against new "destroyBean(Object)" method in AutowireCapableBeanFactory. LocalValidatorFactoryBean adapts Spring-provided ParameterNameDiscoverer onto Bean Validation 1.1's ParameterNameProvider mechanism. LocalValidatorFactoryBean reflectively adapts between the different ResourceBundleLocator SPI location in Hibernate Validator 4.2 versus 5.0. LocalValidatorFactoryBean implements Bean Validation 1.1 "close" method. Note: We still compile against Bean Validation 1.0 in order to not have to implement "forExecutables()" and "getParameterNameDiscoverer()" in LocalValidatorFactoryBean, SpringValidatorAdapter and CustomValidatorBean. Implementing those methods would imply references to Bean Validation 1.1 interfaces that break runtime compatibility with Bean Validation 1.0. Unfortunately, this means that all Bean Validation 1.1 API access has to be done via reflection. Issue: SPR-8199
-
- 28 3月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
JSR-236 support, in particular adapting to JSR-236 Triggers and exposing additional metadata through ManagedTasks This is built into ConcurrentTaskExecutor and ConcurrentTaskScheduler now, automatically detecting the JSR-236 ExecutorService variants and adapting to them. Issue: SPR-8195
-
- 20 3月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 19 3月, 2013 6 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-10388
-
- 13 3月, 2013 2 次提交
-
-
由 Juergen Hoeller 提交于
Just AsyncAnnotationBeanPostProcessor switches "beforeExistingAdvisors" to "true" by default. So effectively, MethodValidation/PersistenceExceptionTranslationPostProcessor apply after existing advisors by default again, fixing the 3.1->3.2 regression. Issue: SPR-10309
-
由 Juergen Hoeller 提交于
Specifically, our CallbackFilter doesn't hold an implicit reference to the containing ConfigurationClassEnhancer class anymore. Issue: SPR-10307
-