- 08 12月, 2015 2 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13696
-
由 Juergen Hoeller 提交于
-
- 07 12月, 2015 5 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13763
-
由 Juergen Hoeller 提交于
Issue: SPR-13765
-
由 Juergen Hoeller 提交于
Issue: SPR-13764
-
由 Juergen Hoeller 提交于
AnnotationConfigWebApplicationContext allows for custom AnnotatedBeanDefinitionReader/ClassPathBeanDefinitionScanner Issue: SPR-9324
-
- 05 12月, 2015 2 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13762
-
- 04 12月, 2015 5 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-13761
-
由 Juergen Hoeller 提交于
Issue: SPR-13760
-
由 Juergen Hoeller 提交于
Issue: SPR-13759
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
- 03 12月, 2015 3 次提交
-
-
由 Juergen Hoeller 提交于
Includes a trivial refinement of RestTemplate's ResourceAccessException message. Issue: SPR-13755
-
由 Juergen Hoeller 提交于
Issue: SPR-13755
-
由 Rossen Stoyanchev 提交于
Issue: SPR-13745
-
- 02 12月, 2015 9 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13753
-
由 Juergen Hoeller 提交于
Issue: SPR-13750
-
由 Juergen Hoeller 提交于
Issue: SPR-13752
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
Fixed a bug where the URL content negotiation "format" parameter values were case sensitive and only lowercase values were accepted. For example, URL query parameter format=json returned the appropriate JSON response but format=JSON resulted in a HttpMediaTypeNotAcceptableException and returned: 406 - The resource identified by this request is only capable of generating responses with characteristics not acceptable according to the request "accept" headers. When the MappingMediaTypeFileExtensionResolver is constructed, it is passed a map containing the media type key to MediaType mappings defined in the ContentNegotiationConfigurer. In the constructor of MappingMediaTypeFileExtensionResolver, the keys are converted to lowercase and the mappings of keys to MediaTypes are added to the ConcurrentMap<String, MediaType> mediaTypes using the lowercase version of the keys. However, when retrieving the MediaType from a key in the lookupMediaType method, no conversion to lowercase is performed so any value for the URL "format" parameter other than the lowercase version will not return the proper MediaType result. On May 1st, 2014, a change was made to ParameterContentNegotiationStrategy to handle cases where the content negotiation format URL parameter does not result in a match for a MediaType. If no match is found, a HttpMediaTypeNotAcceptableException is thrown resulting in the 406 response above. Prior to this commit, a null was returned instead of throwing an exception so this issue was hidden and appeared to function correctly. To make the media type lookup case insensitive, added a line to the lookupMediaType method in MediaTypeFileExtensionResolver to first convert the extension (media type key) to lowercase prior to attempting to retrieve it from the mediaTypes map. Issue: SPR-13747
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
-
- 01 12月, 2015 9 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
This commit reworks the arrangement to a centralized cache, avoiding any extra reflection attempts if a cache entry is known already. In the course of this, it also enforces toXXX methods to be declared as non-static now (which is the only sensible arrangement anyway). Issue: SPR-13703
-
由 Brian Clozel 提交于
Prior to this change, the resource handling FixedVersionStrategy would be applied on all links that match the configured pattern. This is problematic for relative links and can lead to rewritten links such as "/fixedversion/../css/main.css" which breaks. This commit prevents that Strategy from being applied to such links. Of course, one should avoid to use that VersionStrategy with relative links, but this change aims at not breaking existing links even if it means not prefixing the version as expected. Issue: SPR-13727
-
由 Juergen Hoeller 提交于
Issue: SPR-12926
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
The recent commit 971f04 replaced the use of a NAMES_PATTERN regex in favor of direct parsing in order to deal with nested curly braces. The change also incorrectly replicated this logic which removes a trailing slash after Pattern quoting (and not before): https://github.com/spring-projects/spring-framework/blob/cca037a74df9b87f99858154b47696a9eccf69c8/spring-web/src/main/java/org/springframework/web/util/UriTemplate.java#L207-L210 After some more investigation there doesn't appear to be any scenario where the quoted pattern would end with a trailing slash. It should always end with \E (end of quote) or a ")" (end of group). Nor are there any failing tests so this commit removes the logic altogether. Issue: SPR-13705
-
由 Juergen Hoeller 提交于
This commit undoes the previous refinement and rather documents the original behavior. Issue: SPR-13739
-
由 Juergen Hoeller 提交于
Issue: SPR-13741
-
由 Juergen Hoeller 提交于
This commit refines getMergedBeanDefinition's scope adaptation algorithm for inner beans, never leaving a custom scope within a containing bean of a different scope. The inner bean's scope will either be aligned with the containing bean's scope (matching the effective state) or be switched to prototype in case of an outer singleton (indicating that no singleton state management is desired). Issue: SPR-13739
-
- 30 11月, 2015 4 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-13731
-
由 Juergen Hoeller 提交于
JodaTimeFormatterRegistrar defensively checks whether Joda-Time 2.x is present (for Joda-Time 1.x tolerance on the classpath) Also switches 4.2.4's new formatter implementations to package visibility, just in case they'll be superseded by another variant in the future. Issue: SPR-13730
-
由 Juergen Hoeller 提交于
Includes polishing of related conversion exception messages. Issue: SPR-13703
-
- 27 11月, 2015 1 次提交
-
-
由 Juergen Hoeller 提交于
-