- 04 5月, 2015 16 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12977
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12962
-
由 Sam Brannen 提交于
Issue: SPR-11514
-
由 Brian Clozel 提交于
Issue: SPR-12469
-
由 Sam Brannen 提交于
This commit adds additional context to the exception message generated when two candidate methods are discovered in MvcUriComponentsBuilder's getMethod(Class<?>, String, Object...). Issue: SPR-12977
-
由 Sam Brannen 提交于
This commit introduces a new fromMethodNameWithBridgedMethod() test in MvcUriComponentsBuilderTests which is currently disabled via @Ignore until this bug is resolved. Issue: SPR-12977
-
由 Brian Clozel 提交于
When used in combination with GzipResourceResolver, the CachingResourceResolver does not properly cache results, since it only takes the request path as a input for cache key generation. Here's an example of that behavior: 1. an HTTP client requests a resource with `Accept-Encoding: gzip`, so the GzipResourceResolver can resolve a gzipped resource. 2. the configured CachingResourceResolver caches that resource. 3. another HTTP client requests the same resource, but it does not support gzip encoding; the previously cached gzipped resource is still returned. This commit uses the presence/absence of gzip encoding support as an input in cache keys generation. Issue: SPR-12982
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11541
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11541
-
由 Rossen Stoyanchev 提交于
Before this change AbstractHandlerMethodMapping contained multiple maps all containing different kinds of mapping meta-data. After the change a MappingDefinitionRegistry inner class encapsulates these fields along with their initialization code. Issue: SPR-11541
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11541
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12960
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12956
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12955
-
- 03 5月, 2015 2 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
Issue: SPR-12969
-
- 02 5月, 2015 1 次提交
-
-
由 Sam Brannen 提交于
-
- 30 4月, 2015 2 次提交
-
-
由 Stephane Maldini 提交于
-
由 Stephane Maldini 提交于
-
- 27 4月, 2015 4 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
This commit fixes recent build failures involving MessageBrokerBeanDefinitionParserTests and NoClassDefFoundError: io/netty/channel/nio/NioEventLoopGroup.
-
由 Sam Brannen 提交于
This commit documents the status quo for the getMetaAnnotationTypes() method in AnnotatedElementUtils and adds appropriate regression tests to AnnotatedElementUtilsTests. In addition, this commit also introduces a SimpleAnnotationProcessor base class in AnnotatedElementUtils. Issue: SPR-11514
-
- 26 4月, 2015 2 次提交
-
-
由 Sam Brannen 提交于
This commit documents return values throughout AnnotatedElementUtils and improves the documentation for the internal Processor API. Issue: SPR-11514
-
由 Sam Brannen 提交于
Prior to this commit it was possible for two @BootstrapWith annotations to be 'present' on a test class -- for example, via competing custom composed annotations. However, only one of the annotations will ever be used to bootstrap the TestContext Framework. Thus, in such scenarios one of the annotations will be silently ignored. This commit introduces a check for such scenarios. BootstrapUtils' resolveTestContextBootstrapper() method now throws an IllegalStateException if more than one @BootstrapWith annotation is 'present' on a given test class. Issue: SPR-12602
-
- 25 4月, 2015 4 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-12932
-
由 Sam Brannen 提交于
Issue: SPR-12738
-
由 Sam Brannen 提交于
This commit consistently documents the 'element' and 'annotationType' method arguments throughout AnnotatedElementUtils. In addition, this commit introduces assertions against preconditions for all 'element' and 'annotationType' method arguments. Issue: SPR-11514
-
由 Rob Winch 提交于
Previously MockHttpServletRequestBuilder merge method would append the parent's (default) RequestPostProcessor implementations to the end. This means that the default RequestPostProcessor implementations would override values set by previous RequestPostProcessor implementations. This commit ensures that the default RequestPostProcessor are preformed first so that additional RequestPostProcessor implementations override the defaults. Issue: SPR-12945
-
- 24 4月, 2015 7 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-12928
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12296
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12296
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12599
-
由 Stephane Maldini 提交于
Issue: SPR-12599
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
This commit introduces support for finding annotations on abstract, bridge, and interface methods in AnnotatedElementUtils. - Introduced dedicated findAnnotationAttributes() methods in AnnotatedElementUtils that provide first-class support for processing methods, class hierarchies, interfaces, bridge methods, etc. - Introduced find/get search algorithm dichotomy in AnnotatedElementUtils which is visible in the public API as well as in the internal implementation. This was necessary in order to maintain backwards compatibility with the existing API (even though it was undocumented). - Reverted all recent changes made to the "get semantics" search algorithm in AnnotatedElementUtils in order to ensure backwards compatibility, and reverted recent changes to JtaTransactionAnnotationParser and SpringTransactionAnnotationParser accordingly. - Documented internal AnnotatedElementUtils.Processor<T> interface. - Enabled failing tests and introduced findAnnotationAttributesFromBridgeMethod() test in AnnotatedElementUtilsTests. - Refactored ApplicationListenerMethodAdapter.getCondition() and enabled failing test in TransactionalEventListenerTests. - AnnotationUtils.isInterfaceWithAnnotatedMethods() is now package private. Issue: SPR-12738, SPR-11514, SPR-11598
-
- 23 4月, 2015 2 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-