- 15 11月, 2017 3 次提交
-
-
由 sdeleuze 提交于
Issue: SPR-16199
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-15982
-
- 14 11月, 2017 13 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 sdeleuze 提交于
Issue: SPR-16194
-
由 sdeleuze 提交于
Autowiring implicitely Kotlin primary constructors when there are secondary constructors has side effects on ConstructorResolver. It seems reasonable to require explicit @Autowired annotation in such case. With this commit, implicit autowiring of Kotlin primary constructors is only performed when there is a primary constructor defined alone or with a default constructor (define explicitly or generated via the kotlin-noarg compiler plugin or via optional constructor parameters with default values). Issue: SPR-16022
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15700
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15700
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-16191
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-16192
-
由 Juergen Hoeller 提交于
Issue: SPR-16179
-
由 Juergen Hoeller 提交于
Issue: SPR-16177
-
- 13 11月, 2017 3 次提交
-
-
由 diesieben07 提交于
The EXTENSION_RECEIVER parameter of Kotlin's extension methods appear as normal method parameters to Java and thus require a name. The synthetic name "$receiver" is used here, as it is not a valid Kotlin identifier, but valid in Java. Issue: SPR-16119
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
- 12 11月, 2017 1 次提交
-
-
由 Juergen Hoeller 提交于
HibernateJpaVendorAdapter sets connection release mode ON_CLOSE in non-PersistenceUnitInfo bootstrap scenario Issue: SPR-16162
-
- 11 11月, 2017 9 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-15964
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16172
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-16162
-
由 Juergen Hoeller 提交于
Issue: SPR-16173
-
由 Juergen Hoeller 提交于
Issue: SPR-16142
-
由 Juergen Hoeller 提交于
Issue: SPR-16080
-
由 Rossen Stoyanchev 提交于
-
- 10 11月, 2017 9 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16187
-
由 Rossen Stoyanchev 提交于
-
由 Arjen Poutsma 提交于
This commit uses the existing CompositeByteBuf if present, as opposed to creating a new composite for every call to NettyDataBuffer.write(ByteBuf...) Issue: SPR-16180
-
由 Rossen Stoyanchev 提交于
It seems to work.
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 anton_bondarenko 提交于
-
由 Rossen Stoyanchev 提交于
Practically no changes to RxNetty for a year and efforts underway to rebuild 0.6.x based on a current Reactor Netty base. Aside from the extra time to run integration tests having two Netty-based servers can also cause false alarms such as ByteBuf leaks related to RxNetty.
-
由 Rossen Stoyanchev 提交于
This commit adds support for configuring static resource locations with a charset to be applied to relative paths.
-
- 09 11月, 2017 2 次提交
-
-
由 Arjen Poutsma 提交于
Issue: SPR-16121
-
由 Rossen Stoyanchev 提交于
Also remove ErrorDeferredResultProcessingInterceptor which was meant to be package private to begin with as its peer ErrorCallableProcessingInterceptor (also removed).
-