- 11 1月, 2017 4 次提交
-
-
由 Sebastien Deleuze 提交于
This commit also improve significantly Kotlin extensions documentation. Issue: SPR-15127
-
由 Sebastien Deleuze 提交于
-
由 Sebastien Deleuze 提交于
Issue: SPR-15126
-
由 Sebastien Deleuze 提交于
val context = GenericApplicationContext { registerBean<Foo>() registerBean { Bar(it.getBean<Foo>()) } } Issue: SPR-15126
-
- 10 1月, 2017 6 次提交
-
-
由 Mario Arias 提交于
Issue: SPR-15119
-
由 Sebastien Deleuze 提交于
Issue: SPR-15118
-
由 Sebastien Deleuze 提交于
Put the lambda parameter at the end and use a function instead of a supplier to be able to register beans like this: val context = GenericApplicationContext() context.registerBean(Foo::class) context.registerBean{ Bar(it.getBean(Foo::class)) } Issue: SPR-15118
-
由 Sebastien Deleuze 提交于
Based on an idea from Mario Arias, we can avoid requiring specifying explicitly Supplier lambda type in Kotlin API by declaring the supplier parameter as "crossinline supplier: () -> T" instead of "supplier: Supplier<T>". Issue: SPR-15118
-
由 Sebastien Deleuze 提交于
For now if sharedEngine is set to false, a new ScriptEngine instance is created for each request. Issue: SPR-15063
-
由 Juergen Hoeller 提交于
-
- 09 1月, 2017 1 次提交
-
-
由 Sebastien Deleuze 提交于
Issue: SPR-15112
-
- 07 1月, 2017 5 次提交
-
-
由 Sam Brannen 提交于
After the upgrade to JUnit Jupiter 5.0 M3, JUnit Jupiter tests in the Spring build were no longer executed due to the introduction of a default test class name pattern. This commit addresses this issue by making use of the @IncludeClassNamePatterns to specify that *TestCase test classes should be executed within the org.springframework.test.context.junit.jupiter package.
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
Issue: SPR-15106
-
- 05 1月, 2017 3 次提交
-
-
由 Brian Clozel 提交于
Prior to this commit, the `ResourceHttpMessageConverter` would support converting from an `HttpInputMessage` to a `InputStreamResource`. This is valid when reading resources on the server side, but it's not compatible with the way `RestTemplate` works. The API exposed by `RestOperations` imply that the HTTP server response should be fully consumed and properly closed by the time the `exchange` method returns. In other words, this HTTP client does not support streaming the HTTP response. This commit allows the `ResourceHttpMessageConverter` to be configured to disable read streaming when used in `RestTemplate`. Issue: SPR-14882
-
由 Stephane Nicoll 提交于
* pr/1284: Implement MessagingException.toString()
-
由 Gary Russell 提交于
Issue: SPR-15091 Closes gh-1284
-
- 04 1月, 2017 8 次提交
-
-
由 Stephane Nicoll 提交于
* pr/1281: Remove use of Boolean constructors
-
由 Philippe Marschall 提交于
Codacy warns us that there are several references to Boolean constructors in the tests. Direct usage of the Boolean constructor is discouraged and even deprecated in Java 9 [1]. Boolean constructor use can easily be replaced with the constant instances. This commit contains the following changes: - replace references to Boolean constructors with boolean constants in JSP tag tests - update the copyright year where necessary - BooleanComparatorTests is intentionally left unchanged as it should also work with the non-constant instances correctly [1] http://download.java.net/java/jdk9/docs/api/java/lang/Boolean.html#Boolean-boolean- Issue: SPR-15076
-
由 Stephane Nicoll 提交于
* pr/1282: Avoid use of double constructor of BigDecimal
-
由 Philippe Marschall 提交于
Codacy warns about an Error Prone [1] use of the double constructor of BigDecimal in tests. The reason given is that it is a source of precision loss if the number does not have an exact double representation. The recommendation is to use the String constructor of BigDecimal instead as it does not require using a lossy argument. This commit contains the following changes: - replace usage of the double constructor of BigDecimal with the String constructor of BigDecimal in JdbcTemplateQueryTests - update the copyright year [1] http://errorprone.info/bugpattern/BigDecimalLiteralDouble Issue: SPR-15077
-
由 Rob Winch 提交于
Issue: SPR-15088
-
由 Sebastien Deleuze 提交于
Kotlin 1.1-M04 has a bug that makes the generated bytecode not compatible with Kotlin 1.0.x. This bug should be fixed in Kotlin 1.1-M05.
-
由 Stephane Nicoll 提交于
* pr/1280: Remove String#toCharArray from ScriptUtils
-
由 Philippe Marschall 提交于
ScriptUtils contains two calls to String#toCharArray for the sole purpose to iterating over all chars in a String. Not only is this unnecessary and can be replaced with String#charAt it also causes additional allocator and heap pressure because String#toCharArray rather than returning the backing array (which is gone in Java 9) creates a copy. This commit contains the following changes: - remove String#toCharArray from ScriptUtils and replace with String#charAt Issue: SPR-15075
-
- 03 1月, 2017 1 次提交
-
-
由 Brian Clozel 提交于
Prior to this commit, the `ResourceRegionHttpMessageConverter` would rely on the default implementation of `getDefaultContentType` to guess the default Content-Type of the resource region to be written to the HTTP response. That implementation fetches the first media type provided in the HTTP request "Accept" header. This behavior is not correct when converting resources and this commits aligns this converter with the `ResourceHttpMessageConverter` which uses JAF to guess the correct Content-Type of the given resource, or just returns "application/octet-stream" as a default value. Issue: SPR-15041
-
- 01 1月, 2017 2 次提交
-
-
由 Sebastien Deleuze 提交于
Kotlin JSR 223 support currently requires kotlin-script-util dependency (jcabi-aether, maven-core and aether-api can be excluded since they are only used for live import of dependencies and bring a lot of JARs in the classpath) and a /META-INF/services/javax.script.ScriptEngineFactory file specifying the ScriptEngineFactory to use, in that case org.jetbrains.kotlin.script.jsr223.KotlinJsr223JvmLocalScriptEngineFactory. Issue: SPR-15059
-
由 Sebastien Deleuze 提交于
Needed for Kotlin script and JSR 223 support, and a good target for Spring Framework 5.0 since it will allow features like generating Java 8 bytecode, JDK 9 support, annotation array attribute single value without arrayOf(), etc. We ensure Kotlin 1.0 compatibility by setting apiVersion and languageVersion compiler options to 1.0. Issue: SPR-15059
-
- 30 12月, 2016 10 次提交
-
-
由 Stephane Nicoll 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-15072
-
由 Juergen Hoeller 提交于
Issue: SPR-15071
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-15069
-
由 Juergen Hoeller 提交于
Issue: SPR-14692 Issue: SPR-15067
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-