- 28 6月, 2016 2 次提交
-
-
由 Rossen Stoyanchev 提交于
As of 4.3 ResourceHttpRequestHandler delegates to the configured ContentNegotiationManager, or one created internally, to look up the media type for are resource. This commit ensures the internally created ContentNegotiationManager is correctly injected with the ServletContext through which it can perform lookups as before. Also the ServletPathContentNegotiationStrategy now checks the ServletContext first and then delegates to its parent the PathContentNegotiationStrategy and not vice versa. This is consistent with how handleNoMatch (also in the same class) works and also matches how ResourceHttpRequestHandler worked before 4.3. Issue: SPR-14368
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14321
-
- 27 6月, 2016 3 次提交
-
-
由 Brian Clozel 提交于
This commit sets the response content type to "text/event-stream;charset=UTF-8". Even if the SSE spec says that the encoding should always be UTF-8 and that specifying the charset is optional, we're setting it in all cases, since some containers might use the default encoding "ISO-8859-1" and confuse HTTP clients. Issue: SPR-14407
-
由 Juergen Hoeller 提交于
Issue: SPR-14406
-
由 Juergen Hoeller 提交于
Issue: SPR-14385
-
- 26 6月, 2016 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14400
-
由 Juergen Hoeller 提交于
Issue: SPR-14399
-
- 24 6月, 2016 3 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14393
-
由 Juergen Hoeller 提交于
HibernateJpaVendorAdapter and LocalSessionFactoryBuilder enforce Hibernate 5.2's connection handling mode DELAYED_ACQUISITION_AND_HOLD Issue: SPR-14393
-
由 Juergen Hoeller 提交于
Issue: SPR-14393
-
- 23 6月, 2016 5 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14394
-
由 Brian Clozel 提交于
This commit updates AbstractHandlerExceptionResolver to only log at the WARN level exceptions that are actually resolved by the ExceptionResolver. In case developers wish to log each time an ExceptionResolver is called, a DEBUG level log is still available. Issue: SPR-14392
-
由 Sam Brannen 提交于
Issue: SPR-14367
-
由 Sam Brannen 提交于
Prior to this commit, any attempt to include a bean of type ServletServerContainerFactoryBean in the WebApplicationContext for an integration test class annotated with @WebAppConfiguration in conjunction the Spring TestContext Framework (TCF) would have resulted in an IllegalStateException stating that "A ServletContext is required to access the javax.websocket.server.ServerContainer instance." In such scenarios, the MockServletContext was in fact present in the WebApplicationContext; however there was no WebSocket ServerContainer stored in the ServletContext. This commit addresses this issue by introducing the following. - MockServerContainer: a private mock implementation of the javax.websocket.server.ServerContainer interface. - MockServerContainerContextCustomizer: a ContextCustomizer that instantiates a new MockServerContainer and stores it in the ServletContext under the attribute named "javax.websocket.server.ServerContainer". - MockServerContainerContextCustomizerFactory: a ContextCustomizerFactory which creates a MockServerContainerContextCustomizer if WebSocket support is present in the classpath and the test class is annotated with @WebAppConfiguration. This factory is registered by default via the spring.factories mechanism. Issue: SPR-14367
-
由 Sam Brannen 提交于
Issue: SPR-14367
-
- 22 6月, 2016 5 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14388
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14373
-
由 Juergen Hoeller 提交于
Issue: SPR-14328
-
由 Rossen Stoyanchev 提交于
When comparing multiple matching @RequestMapping's, the HTTP method condition has the lowest precedence. It's mainly about ensuring an explicit mapping wins over an implicit (i.e. no method) one. As of 4.3 HTTP HEAD is handled automatically for controller methods that match to GET. However an explicit mapping HTTP HEAD allows an application to take control. This commit ensures that for HTTP HEAD requests the HTTP method condition is checked first which means that an explicit HEAD mapping now trumps all other conditions. Normally we look for the most specific matching @RequestMapping. For HTTP HEAD we now look for the most specific match among @RequestMapping methods with a HEAD mapping first. Issue: SPR-14383
-
- 21 6月, 2016 2 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-14385
-
- 20 6月, 2016 4 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-10454
-
由 Juergen Hoeller 提交于
Issue: SPR-14379
-
由 Juergen Hoeller 提交于
-
- 18 6月, 2016 2 次提交
-
-
由 Rossen Stoyanchev 提交于
Even before this change SockJS sessions always cancelled the heartbeat task first prior to sending messages. However when the heartbeat task is already in progress, cancellation of it is not enough and we must wait until the heartbeat is sent. This commit adds a heartbeat write lock which is obtained and held during the sending of a heartbeat. Now when sessions send a message they still cancel the heartbeat task but if that fails they also wait for the heartbeat write lock. Issue: SPR-14356
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14372
-
- 17 6月, 2016 3 次提交
-
-
由 nkjackzhang 提交于
-
由 Stephane Nicoll 提交于
* pr/1082: Move <a> out of @code
-
由 nkjackzhang 提交于
Closes gh-1082
-
- 16 6月, 2016 4 次提交
-
-
由 Stephane Nicoll 提交于
Closes gh-14366
-
由 Stephane Nicoll 提交于
* pr/1080: Polish contribution Fix typo in javadoc
-
由 Stephane Nicoll 提交于
Closes gh-1080
-
由 nkjackzhang 提交于
See gh-1080
-
- 15 6月, 2016 5 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-14365
-
由 Sam Brannen 提交于
Issue: SPR-14362
-
由 Juergen Hoeller 提交于
Issue: SPR-14364
-
由 Juergen Hoeller 提交于
Issue: SPR-14358
-
由 Sam Brannen 提交于
ReflectionTestUtils invokes toString() on target objects in order to build exception and logging messages, and prior to this commit problems could occur if the invocation of toString() threw an exception. This commit addresses this issue by ensuring that all invocations of toString() on target objects within ReflectionTestUtils are performed safely within try-catch blocks. Issue: SPR-14363
-