- 15 7月, 2016 6 次提交
-
-
由 Arjen Poutsma 提交于
- Added Woodstox before Aalto in the spring-web build, so that Woodstox is used as StAX implementation, and not the less featured Aalto. - Hardcoded Aalto dependency in XmlEventDecoder, instead of relying on the StAX XMLInputFactory.
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rob Winch 提交于
-
- 14 7月, 2016 13 次提交
-
-
由 Sam Brannen 提交于
Issue: SPR-4365
-
由 Sam Brannen 提交于
Issue: SPR-14459
-
由 nkjackzhang 提交于
Closes gh-1110
-
由 Stephane Nicoll 提交于
Closes gh-1070
-
由 spodgurskiy 提交于
This commit fix a potential `ArrayIndexOutOfBoundsException` if `lazyLoadArguments` is called with an empty variable argument. See gh-1070
-
由 Juergen Hoeller 提交于
Issue: SPR-14438
-
由 Juergen Hoeller 提交于
Issue: SPR-14457
-
由 Juergen Hoeller 提交于
Issue: SPR-14457
-
由 Juergen Hoeller 提交于
Issue: SPR-14455
-
由 Sam Brannen 提交于
Issue: SPR-14431
-
由 Sam Brannen 提交于
Prior to this commit, a dynamic test in FailingBeforeAndAfterMethodsSpringExtensionTestCase was failing but for the wrong reason. Namely, the @Configuration class was private which resulted in an IllegalStateException being thrown, when in fact an AssertionFailedError was expected. This commit addresses this by introducing an explicit check for an AssertionFailedError. Issue: SPR-4365
-
由 Sam Brannen 提交于
Prior to this commit, if multiple TestExecutionListener 'after' methods threw an exception, only the first such exception was rethrown. Subsequent exceptions were logged, but there was no way to access or process them other than via the log file. This commit addresses this shortcoming by making use of the support for suppressed exceptions introduced in Java 7. Specifically, if multiple TestExecutionListener 'after' methods throw an exception, the first exception will be rethrown with subsequent exceptions suppressed in the first one. Issue: SPR-14459
-
由 Sam Brannen 提交于
-
- 13 7月, 2016 12 次提交
-
-
由 Sam Brannen 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14452
-
由 Juergen Hoeller 提交于
This commit also aligns ResourceUrlProvider's and RequestMappingInfo's UrlPathHelper setter/getter signatures. Issue: SPR-14454
-
由 Arjen Poutsma 提交于
Moved ResponseBodyProcessor creation from constructor to writeWithInternal(), in preparation of supporting both Publisher<DataBuffer> as well as Publisher<Publisher<DataBuffer>>.
-
由 Arjen Poutsma 提交于
Moved log4j.properties from the main source tree to the test tree.
-
由 Arjen Poutsma 提交于
In preparation of supporting both Publisher<DataBuffer> and Publisher<Publisher<DataBuffer>> as response body, moved RequestBodyPublisher and ResponseBodyProcessor into ServletServerHttpRequest and ServletServerHttpResponse respectively.
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
-
由 Arjen Poutsma 提交于
Refactored Publisher<Void> in AbstractResponseBodyProcessor into separate ResponseBodyWriteResultPublisher.
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Vladimir L 提交于
-
- 12 7月, 2016 9 次提交
-
-
由 Brian Clozel 提交于
-
由 Sam Brannen 提交于
A "What's New" page has been created in the Spring Framework wiki: https://github.com/spring-projects/spring-framework/wiki/What's-New-in-the-Spring-Framework This commit therefore links to the new wiki page from the appendix of the reference manual and deletes the existing "What's New" chapter from the reference manual. Issue: SPR-14449
-
由 Sam Brannen 提交于
This commit makes use of the new Supplier<String> variants of utility methods in org.springframework.util.Assert within the spring-test module. Issue: SPR-14450
-
由 Sam Brannen 提交于
This commit makes use of the new Supplier<String> variants of utility methods in org.springframework.util.Assert within the spring-core module. Issue: SPR-14450
-
由 Sam Brannen 提交于
Prior to this commit, utility methods in org.springframework.util.Assert accepted String arguments for custom error messages. Such Strings are evaluated (e.g., concatenated) eagerly, and for performance reasons, it was therefore not always possible to make use of these utility methods. Consequently, there are several places in the code base that "inline" identical functionality in order to lazily evaluate error message concatenation and avoid an unnecessary performance penalty. This leads to verbose code like the following. if (!contextPath.startsWith("/")) { throw new IllegalArgumentException("contextPath '" + contextPath + "' must start with '/'."); } if (contextPath.endsWith("/")) { throw new IllegalArgumentException("contextPath '" + contextPath + "' must not end with '/'."); } This commit addresses this shortcoming by introducing Supplier<String> variants of all utility methods in org.springframework.util.Assert that allow custom error messages to be evaluated lazily via a lambda expression that is only evaluated if the assertion fails. This results in a simplification of the previous examples as follows. Assert.isTrue(contextPath.startsWith("/"), () -> "contextPath '" + contextPath + "' must start with '/'."); Assert.isTrue(!contextPath.endsWith("/"), () -> "contextPath '" + contextPath + "' must not end with '/'."); Issue: SPR-14450
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
Issue: SPR-14247
-
由 Arjen Poutsma 提交于
-
由 Stephane Maldini 提交于
-