- 31 7月, 2018 1 次提交
-
-
由 stsypanov 提交于
-
- 28 7月, 2018 2 次提交
-
-
由 Pascal Schumacher 提交于
Issue: SPR-16993 Obvious Fix
-
由 Juergen Hoeller 提交于
-
- 27 7月, 2018 14 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-17090
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16993
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17091
-
由 Rossen Stoyanchev 提交于
Based on discussion under https://github.com/spring-projects/spring-framework/pull/1901
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-17096
-
由 Rossen Stoyanchev 提交于
Issue: SPR-17094
-
由 Rossen Stoyanchev 提交于
-
由 Bhavani Shekhawat 提交于
Fix the error message when PropertySources are not applied
-
由 Juergen Hoeller 提交于
Issue: SPR-17095
-
- 26 7月, 2018 9 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Johnny Lim 提交于
-
由 Johnny Lim 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-17093
-
由 Hannes Metssalu 提交于
'AbstractFactoryBean#getEarlySingletonInstance' documentation mentions "eager singleton". I'm quite sure it should be fixed to "early singleton".
-
由 Juergen Hoeller 提交于
Issue: SPR-15338
-
由 Rossen Stoyanchev 提交于
Sample output at TRACE: ``` DispatcherServlet - Initializing Servlet 'org.springframework.web.servlet.DispatcherServlet-7a8c8dcf' AnnotationConfigWebApplicationContext - Refreshing WebApplicationContext for namespace 'org.springframework.web.servlet.DispatcherServlet-7a8c8dcf-servlet', started on Wed Jul 25 17:46:38 EDT 2018 AnnotationConfigWebApplicationContext - Registering [org.springframework.web.servlet.mvc.method.annotation.RequestPartIntegrationTests$CommonsMultipartResolverTestConfig] AnnotationConfigWebApplicationContext - No 'messageSource' bean, using [Empty MessageSource] AnnotationConfigWebApplicationContext - No 'applicationEventMulticaster' bean, using [SimpleApplicationEventMulticaster] AnnotationConfigWebApplicationContext - No 'lifecycleProcessor' bean, using [DefaultLifecycleProcessor] ... DispatcherServlet - Initialization completed in 3361 ms ``` Issue: SPR-16946
-
由 Juergen Hoeller 提交于
Includes related polishing in the advice interceptor implementations. Issue: SPR-17088
-
由 Juergen Hoeller 提交于
-
- 25 7月, 2018 14 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Includes nullability declarations for the protobuf package. Issue: SPR-15776
-
由 Juergen Hoeller 提交于
Issue: SPR-17086
-
由 Juergen Hoeller 提交于
Issue: SPR-16585 Issue: SPR-17012
-
由 Sebastien Deleuze 提交于
Issue: SPR-17083
-
由 Rossen Stoyanchev 提交于
Issue: SPR-16609
-
由 Rossen Stoyanchev 提交于
-
由 sdeleuze 提交于
This commit introduces Protobuf support in WebFlux via dedicated codecs. Flux<Message> are serialized/deserialized using delimited Protobuf messages with the size of each message specified before the message itself. In that case, a "delimited=true" parameter is added to the content type. Mono<Message> are expected to use regular Protobuf message format (without the size prepended before the message). Related HttpMessageReader/Writer are automatically registered when the "com.google.protobuf:protobuf-java" library is detected in the classpath, and can be customized easily if needed via CodecConfigurer, for example to specify protocol extensions via the ExtensionRegistry based constructors. Both "application/x-protobuf" and "application/octet-stream" mime types are supported. Issue: SPR-15776
-
由 Juergen Hoeller 提交于
-
由 Brian Clozel 提交于
Prior to this commit, controller handlers (regular and exception handlers as well) would not overwrite existing HTTP response headers on the exchange. This would lead to situations where Content-Type values set during the initial handling phase would not be overwritten when handling an error later on. This commit aligns the implementation of that result handler on the Spring MVC one in that regard. Issue: SPR-17082
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
Preparation for SPR-17072
-
由 Rossen Stoyanchev 提交于
Preparation for SPR-17072
-