- 12 9月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-12181
-
- 04 9月, 2014 3 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-11310 Issue: SPR-10548
-
- 22 8月, 2014 3 次提交
-
-
由 Juergen Hoeller 提交于
Revised ResourcePropertySource in order to avoid ConfigurationClassProcessor's AnnotationPropertySource subclass Issue: SPR-12115
-
由 Phillip Webb 提交于
Fix CompositePropertySourceTests which fails when run we debug logging.
-
由 Phillip Webb 提交于
Rework the @PropertySource parsing logic recently changed in commit 7c608886 to deal with the same source appearing on a @Configuration class and an @Import class. Processing now occurs in a single sweep, with any previously added sources being converted to a CompositePropertySource. Issue: SPR-12115
-
- 20 8月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-12095
-
- 13 8月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-12078
-
- 06 8月, 2014 1 次提交
-
-
由 David Haraburda 提交于
Prior to this commit, given an enum which implements some interface, GenericConversionService would select the String -> Enum converter even if a converter for String -> SomeInterface was registered. This also affected converters that were registered for String -> SomeBaseInterface, when SomeInterface extended SomeBaseInterface. This change modifies the behavior of the private method getClassHierarchy() by placing Enum.class as late as possible, pretty much the same way as Object.class is handled. Issue: SPR-12050
-
- 16 7月, 2014 2 次提交
-
-
由 Sebastien Deleuze 提交于
Make it possible to use a ListenableFuture with Java 8 lambda expressions, using a syntax like listenableFuture.addCallback(() -> ..., () -> ...); Issue: SPR-11820
-
由 Arjen Poutsma 提交于
The StaxStreamXMLReader no longer handles all whitespace as ignorable whitespace. Issue: SPR-12000
-
- 15 7月, 2014 2 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11660
-
由 Sebastien Deleuze 提交于
In order to be able to use separators like "." (used by default by most broker relays) instead of "/" for destination patterns handling, the PathMatcher used in spring-messaging can now be customized easily thanks to XML websocket namespace or JavaConfig. AntPathMatcher has been updated in order to use the configured path separator instead of an hardcoded "/" for path concatenation. Extension handling is now disabled when the "." separator is configured. Issue: SPR-11660
-
- 10 7月, 2014 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-11746
-
由 Juergen Hoeller 提交于
Issue: SPR-9616
-
- 25 6月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-11898
-
- 17 6月, 2014 3 次提交
-
-
由 Rossen Stoyanchev 提交于
This change modifies the SettableListenableFuture implementation to use internally a ListenableFutureTask created with a "settable" Callable. Issue: SPR-11614
-
由 Mattias Severson 提交于
A SettableListenableFuture implementation of Spring's ListenableFuture The class is inspired by Google Guava’s com.google.common.util.concurrent.SettableFuture, but this implementation uses ReentrantReadWriteLock and CountDownLatch internally to handle thread synchronization. Issue: SPR-11614
-
由 Rossen Stoyanchev 提交于
After this change, java.util.Optional is supported with @RequestParam, @RequestHeader, and @MatrixVariable arguments in Java 8. When Optional is used the required flag is effectively ignored. Issue: SPR-11829
-
- 12 6月, 2014 3 次提交
-
-
由 Brian Clozel 提交于
Prior to this commit, AntPathMatcher had been refactored for SPR-6741. During that process, a key feature has been removed: When comparing two patterns, pattern elements (*, {}, etc) are counted to score those patterns. When a pattern ends with ".*", the ending wildcard should not be counted against pattern elements for this pattern. This commit reintroduces that behavior. Issue: SPR-6741
-
由 Rossen Stoyanchev 提交于
Issue: SPR-6741
-
由 Brian Clozel 提交于
Prior to this commit, "**" and "*" pattern elements had the same priority when comparing two patterns. So when comparing several patterns, the computed order was: 1- /hotels/{hotel}/bookings/{booking} 2- /hotels/** 3- /hotels/{hotel}/bookings/{booking}/customer/{customer} This commit updates the comparator so that patterns ending with "**" (a.k.a "catch-all" patterns) are less specific than the others; in the previous example, the 2nd pattern would then end up last. This commit also optimizes the comparator implementation. Issue: SPR-6741
-
- 05 6月, 2014 2 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Stephane Nicoll 提交于
This commit introduces OrderProvider and OrderProviderComparator, two interfaces designed to externalize how a collection of element is sorted according to their order value. FactoryAwareOrderProvider is an OrderProvider implementation that knows about the objects to order and the corresponding BeanFactory instance. This allows to retrieve additional metadata about the actual instances to sort, such as its factory method. A @Bean method can now holds an additional @order to define the order value that this bean should have when injected as part of a collection or array. Issue: SPR-11310
-
- 31 5月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
ClassMetadata exposes isAnnotation() now, and correctly returns false from hasSuperClass() for interfaces and annotations Issue: SPR-11711
-
- 20 5月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
This commit also includes a JUnit 4 style revision of StringUtilsTests and ObjectUtilsTests. Issue: SPR-11806
-
- 16 5月, 2014 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11793
-
- 13 5月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 09 5月, 2014 2 次提交
-
-
由 Stephane Nicoll 提交于
This commit separates the BackOff configuration from an actual execution. BackOffExecution now contains all the state of a particular execution and BackOff is only meant to start (i.e. create) a new execution. The method "reset" has been removed as its no longer necessary: when an execution does not need to be used for a given operation anymore it can be simply discarded. Issue: SPR-11746
-
由 Stephane Nicoll 提交于
Prior to this commit, DefaultMessageListenerContainer was recovering on failure using a fixed time interval, potentially in an infinite way. This commit adds an extra "backoff" property to the container that permits to fine tune the recovery interval using a BackOff instance. FixedBackOff provides a fixed interval between two attempts and a maximum number of retries. ExponentialBackOff increases an initial interval until a maximum interval has been reached. A BackOff instance can return a special "STOP" time value that indicates that no further attemps should be made. DefaultMessageListenerContainer uses this value to stop the container. protected method "sleepInbetweenRecoveryAttempts" has been renamed to "applyBackOff" and now returns a boolean that indicate if the back off has been applied and a new attempt should now be made. Issue: SPR-11746
-
- 07 5月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-11763
-
- 01 5月, 2014 1 次提交
-
-
由 Juergen Hoeller 提交于
AnnotationMetadataReadingVisitor passes metaAnnotationMap into getMergedAnnotationAttributes algorithm, for finding out about applicable overrides Issue: SPR-11649
-
- 22 4月, 2014 2 次提交
-
-
由 Stephane Nicoll 提交于
-
由 Sam Brannen 提交于
Prior to this commit, invoking the getMergedAnnotationAttributes() method in AnnotationReadingVisitorUtils resulted in mutation of the internal state of the ASM-based annotation metadata supplied to the method. This commit fixes this issue by making a copy of the original AnnotationAttributes for the target annotation before merging attribute values from the meta-annotation hierarchy. This commit also introduces a slight performance improvement by avoiding duplicate processing of the attributes of the target annotation. Issue: SPR-11710
-
- 07 4月, 2014 1 次提交
-
-
由 Stephane Nicoll 提交于
This commit adds support for the JSR-107 cache annotations alongside the Spring's cache annotations, that is @CacheResult, @CachePut, @CacheRemove and @CacheRemoveAll as well as related annotations @CacheDefaults, @CacheKey and @CacheValue. Spring's caching configuration infrastructure detects the presence of the JSR-107 API and Spring's JCache implementation. Both @EnableCaching and the cache namespace are able to configure the required JCache infrastructure when necessary. Both proxy mode and AspectJ mode are supported. As JSR-107 permits the customization of the CacheResolver to use for both regular and exception caches, JCacheConfigurer has been introduced as an extension of CachingConfigurer and permits to define those. If an exception is cached and should be rethrown, it is cloned and the call stack is rewritten so that it matches the calling thread each time. If the exception cannot be cloned, the original exception is returned. Internally, the interceptors uses Spring's caching abstraction by default with an adapter layer when a JSR-107 component needs to be called. This is the case for CacheResolver and CacheKeyGenerator. The implementation uses Spring's CacheManager abstraction behind the scene. The standard annotations can therefore be used against any CacheManager implementation. Issue: SPR-9616
-
- 06 4月, 2014 1 次提交
-
-
由 Sam Brannen 提交于
-
- 01 4月, 2014 1 次提交
-
-
由 Stephane Nicoll 提交于
This commit rationalizes the use of @order so that the standard @Priority annotation can be used instead. The handling of both annotations are now defined in OrderUtils. This also updates the link to the JavaEE API so that we refer to JavaEE7 instead of JavaEE6. Issue: SPR-11639
-
- 26 3月, 2014 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-11608
-
由 Arjen Poutsma 提交于
Improved the SAX to StAX (and vice-versa) bridge exposed via StaxUtils. The old integration had some issues with namespace declaration attributes, brought to light in a XMLUnit upgrade. Issue: SPR-11549
-