- 19 2月, 2016 16 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13956
-
由 Juergen Hoeller 提交于
Issue: SPR-13887
-
由 Stephane Nicoll 提交于
* pr/970: Consistent descriptions for ConfigurationClass
-
由 Andy Wilkinson 提交于
Previously, a ConfigurationClass created from AnnotationMetadata and a ConfigurationClass created from a class would have subtly different descriptions. Given a class named com.example.Foo, the former’s description would be “com.example.Foo”, whereas the latter’s description would be “class com.example.Foo”. This commit updates ConfigurationClass to make the description consistent, preferring the description without “class” in it. Closes gh-970
-
由 Rossen Stoyanchev 提交于
The test failure was caused by the previous commit. The Message resolver now supports payload conversion so it can raise a MessageConversionException, not MethodArgumentTypeMismatchException.
-
由 Phillip Webb 提交于
Refine the optimizations made in 6f55ab69 in order to restore binary compatibility and resolve a regression. Tests of the form pathMatcher.match("/foo/bar/**", "/foo/bar") should return true as this was the behavior in Spring 4.2. Issue: SPR-13913
-
由 Juergen Hoeller 提交于
Issue: SPR-13963
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
The MessageMethodArgumentResolver now also supports applying a MessageConverter to the payload. This is effectively a shortcut for declaring a method with an @Payload argument + MessageHeaders and then creating a new message from the two. Issue: SPR-13288
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13963
-
由 Juergen Hoeller 提交于
Issue: SPR-13961
-
由 Rossen Stoyanchev 提交于
Commit ccd17d introduced a regression where a custom HTTP method would no longer match for an empty @RequestMapping condition. The previous behavior should now be restored. Effectively RequestMethodRequestCondition as before will now match to any HTTP method (even unknown/custom ones) if the methods condition is empty. The only exception is HTTP OPTIONS for which we provide default handling as a fallback (i.e. when not mapped explicitly). Issue: SPR-13130
-
由 Brian Clozel 提交于
This commit adds weak ETag support in ShallowEtagHeaderFilter. This improves the behavior of the filter in tow ways: * weak ETags in request headers such as `W/"0badc0ffee"` will be compared with a "weak comparison" (matching both weak and strong ETags of the same value) * when enabled with the "writeWeakETag" init param, the filter will write weak Etags in its HTTP responses Issue: SPR-13778
-
由 Juergen Hoeller 提交于
Issue: SPR-13959
-
由 Juergen Hoeller 提交于
Issue: SPR-13950
-
- 18 2月, 2016 4 次提交
-
-
由 Juergen Hoeller 提交于
Includes a fix for Query unwrapping before passing it to addNamedQuery. Issue: SPR-13960 Issue: SPR-13957
-
由 Juergen Hoeller 提交于
Issue: SPR-13625
-
由 Juergen Hoeller 提交于
Issue: SPR-13952
-
由 Sam Brannen 提交于
-
- 17 2月, 2016 15 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13930
-
由 Juergen Hoeller 提交于
Issue: SPR-13951
-
由 Brian Clozel 提交于
This change makes clear that this is the intent of the CacheControl API not to provide a way to configure both "no-cache" and "no-store" directives for the "Cache-Control" header. Issue: SPR-13780
-
由 Stephane Nicoll 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 matthew-pearson 提交于
Check that the path is valid and resolvable before checking that the http method is supported. For invalid or unresolvable paths, always respond with a 404.
-
由 Stephane Nicoll 提交于
* pr/957: Polish contribution Decrease allocation rate for CacheOperation
-
由 Stephane Nicoll 提交于
Closes gh-957
-
由 soldierkam 提交于
-
由 Stephane Nicoll 提交于
* pr/960: Polish doc
-
由 logicg8 提交于
Closes gh-960
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-11787
-
由 Juergen Hoeller 提交于
Issue: SPR-13406
-
- 16 2月, 2016 4 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13480
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Use synchonous API for synchonous OkHttp requests
-
由 Arjen Poutsma 提交于
This commit changes the OkHttpClientHttpRequestFactory to use the synchronous OkHttp API for non-async requests, as opposed to synchronizing the async API (which it used to do). Issue: SPR-13942
-
- 13 2月, 2016 1 次提交
-
-
由 Juergen Hoeller 提交于
Support for SmartObjectFactory injection points with programmatic optionality and lenient not-unique handling Issue: SPR-13943
-