forked from spring-projects/spring-framework
-
Notifications
You must be signed in to change notification settings - Fork 0
sync with spring source #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* pr/23071: Polish "Replace with 'Integer.compare()'" Replace with 'Integer.compare()' Closes gh-23071
This commit introduces support for consistent ordering of Properties created by CollectionFactory.createStringAdaptingProperties(). Specifically, the created Properties instance sorts properties alphanumerically based on their keys. Closes gh-23081
Beginning with Spring Framework 5.0, non-null checks for the requiredType in the following methods were inadvertently removed with the internal switch to ResolvableType.forRawClass(requiredType). - BeanFactory.getBean(Class<T>, Object...) - BeanFactory.getBeanProvider(Class<T>) - AutowireCapableBeanFactory.resolveNamedBean(Class<T>) This commit restores those non-null checks. Closes gh-23045
Improve Javadoc Consistently reject Publisher unless using asyncPart Consistently set Content-Type when specified
1. Add contentType and filename options to PartBuilder. 2. Revert recently committed #44659f since asyncPart can't properly support Publisher of Part (only Mono, can't support filename), and replace that with support for Part in the regular part method. Closes gh-23083
This commit renames currentTransaction() to forCurrentTransaction() for greater clarity. Closes gh-23086
Similar to fix applied to Synchronoss implementation in #cef98e.
This commit allows to configure a custom path separator when parsing and matching path patterns with `PathPatternParser`, but also when parsing incoming paths as `PathContainer` instances. Closes gh-23092
Prior to this commit, MockHttpServletRequest.setCookies() produced one Cookie header per supplied cookie, resulting in multiple Cookie headers which violates the specification. This commit fixes this by ensuring that all cookie name-value pairs are stored under a single Cookie header, separated by a semicolon. Closes gh-23074
Prior to Spring Framework 5.1.3, MimeTypeUtils.parseMimeTypes() and MediaType.parseMediaTypes() ignored empty entries, but 5.1.3 introduced a regression in that an empty entry -- for example, due to a trailing comma in the list of media types in an HTTP Accept header -- would result in a "406 Not Acceptable" response status. This commit fixes this by filtering out empty entries before parsing them into MimeType and MediaType instances. Empty entries are therefore effectively ignored. Fixes gh-23241
Prior to this commit, if the user configured an empty path for the targetRequestPath property of a FlashMap, the FlashMapManager threw a StringIndexOutOfBoundsException when saving the output FlashMap for the next request. This commit fixes this by skipping the decoding and normalization of an empty target request path. Fixes gh-23240
The commit deprecates syncBody(Object) in favor of body(Object) which has the same behavior in ServerResponse, WebClient and WebTestClient. It also adds body(Object, Class) and body(Object, ParameterizedTypeReference) methods in order to support any reactive type that can be adapted to a Publisher via ReactiveAdapterRegistry. Related BodyInserters#fromProducer methods are provided as well. Shadowed Kotlin body<T>() extensions are deprecated in favor of bodyWithType<T>() ones, including dedicated Publisher<T> and Flow<T> variants. Coroutines extensions are adapted as well, and body(Object) can now be used with suspending functions. Closes gh-23212
Extension functions need to use reified types to create ParameterizedTypeReference. Closes gh-23185
This commit renames RSocketRequester.RequestSpec data extension to dataWithType to avoid shadowing issues and adds Publisher<T> and Flow<T> variants to provide automatic reified type parameter resolution for those types. It also makes RSocketRequester consistent with the changes introduced via 2b4d6ce in WebFlux.
The new annotation helps to differentiate the handling of connection level frames (SETUP and METADATA_PUSH) from the 4 stream requests. Closes gh-23177
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.