- 24 3月, 2018 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-16620
-
由 Juergen Hoeller 提交于
Issue: SPR-16625 Issue: SPR-16627
-
- 17 2月, 2018 1 次提交
-
-
由 Juergen Hoeller 提交于
(cherry picked from commit 6d11b403)
-
- 18 8月, 2017 1 次提交
-
-
由 Juergen Hoeller 提交于
Bean-derived null values may still get passed into bean properties and injection points but only if those are declared as non-required. Note that getBean will never return null; a manual bean.equals(null) / "null".equals(bean.toString()) check identifies expected null values now. This will only ever happen with custom FactoryBeans or factory methods returning null - and since all common cases are handled by autowiring or bean property values in bean definitions, there should be no need to ever manually check for such a null value received from getBean. Issue: SPR-15829
-
- 17 8月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
Issue: SPR-15869
-
- 30 6月, 2017 1 次提交
-
-
由 Juergen Hoeller 提交于
This commits extends nullability declarations to the field level, formalizing the interaction between methods and their underlying fields and therefore avoiding any nullability mismatch. Issue: SPR-15720
-
- 07 6月, 2017 1 次提交
-
-
由 Juergen Hoeller 提交于
Beyond just formally declaring the current behavior, this revision actually enforces non-null behavior in selected signatures now, not tolerating null values anymore when not explicitly documented. It also changes some utility methods with historic null-in/null-out tolerance towards enforced non-null return values, making them a proper citizen in non-null assignments. Some issues are left as to-do: in particular a thorough revision of spring-test, and a few tests with unclear failures (ignored as "TODO: NULLABLE") to be sorted out in a follow-up commit. Issue: SPR-15540
-
- 01 6月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
Issue: SPR-15540
-
- 27 5月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
This commit introduces 2 new @Nullable and @NonNullApi annotations that leverage JSR 305 (dormant but available via Findbugs jsr305 dependency and already used by libraries like OkHttp) meta-annotations to specify explicitly null-safety of Spring Framework parameters and return values. In order to avoid adding too much annotations, the default is set at package level with @NonNullApi and @Nullable annotations are added when needed at parameter or return value level. These annotations are intended to be used on Spring Framework itself but also by other Spring projects. @Nullable annotations have been introduced based on Javadoc and search of patterns like "return null;". It is expected that nullability of Spring Framework API will be polished with complementary commits. In practice, this will make the whole Spring Framework API null-safe for Kotlin projects (when KT-10942 will be fixed) since Kotlin will be able to leverage these annotations to know if a parameter or a return value is nullable or not. But this is also useful for Java developers as well since IntelliJ IDEA, for example, also understands these annotations to generate warnings when unsafe nullable usages are detected. Issue: SPR-15540
-
- 08 11月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14883 (cherry picked from commit b42d731f)
-
- 27 7月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13188
-
- 06 7月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14433
-
- 05 7月, 2016 1 次提交
-
-
由 Stephane Nicoll 提交于
Issue: SPR-13188
-
- 13 11月, 2015 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13621
-
- 27 2月, 2015 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-12739
-
- 07 12月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-10787
-
- 03 9月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-10508 Issue: SPR-8080
-
- 21 8月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 20 8月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
DefaultSingletonBeanRegistry performs non-synchronized checks for existing entries in dependentBeanMap and containedBeanMap Also adding alias resolution to isDependent's algorithm (for circular dependency detection). Issue: SPR-8834 Issue: SPR-7966
-
- 15 7月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 02 12月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-7966
-
- 26 11月, 2013 1 次提交
-
-
由 Phillip Webb 提交于
Fix remaining Java compiler warnings, mainly around missing generics or deprecated code. Also add the `-Werror` compiler option to ensure that any future warnings will fail the build. Issue: SPR-11064
-
- 25 7月, 2013 1 次提交
-
-
由 Phillip Webb 提交于
Reduce INFO level destroy logging to DEBUG Issue: SPR-10758
-
- 14 5月, 2013 1 次提交
-
-
由 Rob Winch 提交于
Issue: SPR-10130
-
- 29 3月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
Use JDK 1.6's Collections.newSetFromMap instead of manually accessing Maps with dummy Boolean values
-
- 02 1月, 2013 1 次提交
-
-
由 Chris Beams 提交于
This reverts commit 45fa5082, reversing changes made to a312d900.
-
- 29 12月, 2012 2 次提交
-
-
由 Chris Beams 提交于
Issue: SPR-10130
-
由 Chris Beams 提交于
Issue: SPR-10128
-
- 13 12月, 2012 1 次提交
-
-
由 Juergen Hoeller 提交于
In particular, avoiding synchronized Sets and Maps wherever possible (preferring a ConcurrentHashMap even instead of a synchronized Set) and specifying appropriate ConcurrentHashMap initial capacities (even if we end up choosing 16).
-
- 26 11月, 2012 1 次提交
-
-
由 Juergen Hoeller 提交于
Avoid wide locks in order to remove deadlock potential in case of multi-threaded singleton creation/destruction Issue: SPR-10020 Issue: SPR-8471
-
- 09 11月, 2012 2 次提交
-
-
由 Juergen Hoeller 提交于
DefaultSingletonBeanRegistry avoids singletonObjects lock wherever possible for non-singleton factory performance Also fixing setCurrentlyInCreation to use a concurrent Set and to apply to prototype beans as well. Issue: SPR-9819
-
由 Juergen Hoeller 提交于
DefaultSingletonBeanRegistry avoids singletonObjects lock wherever possible for non-singleton factory performance Issue: SPR-9819
-
- 10 10月, 2012 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 31 1月, 2012 1 次提交
-
-
由 Chris Beams 提交于
This renaming more intuitively expresses the relationship between subprojects and the JAR artifacts they produce. Tracking history across these renames is possible, but it requires use of the --follow flag to `git log`, for example $ git log spring-aop/src/main/java/org/springframework/aop/Advisor.java will show history up until the renaming event, where $ git log --follow spring-aop/src/main/java/org/springframework/aop/Advisor.java will show history for all changes to the file, before and after the renaming. See http://chrisbeams.com/git-diff-across-renamed-directories
-
- 12 5月, 2011 1 次提交
-
-
由 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
-
- 08 6月, 2010 1 次提交
-
-
由 Juergen Hoeller 提交于
registerDependentBean resolves to the canonical bean name in order to handle alias references (SPR-7254)
-
- 25 11月, 2008 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 20 11月, 2008 1 次提交
-
-
由 Juergen Hoeller 提交于
EL container integration; support for contextual objects; removal of deprecated Spring 2.0 functionality; Java 5 code style
-
- 23 10月, 2008 1 次提交
-
-
由 Arjen Poutsma 提交于
-