Fix MultipartResolver javadoc implementation refs #48
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
Before this fix MultipartResolver javadoc mentioned that there is only one concrete implementation included in Spring. This was true as of Spring 2.5 but Spring 3.1 added another one, Servlet 3.0 Part API based implementation. This fix changes MultipartResolver javadoc so that the other one, StandardServletMultipartResolver implementation, gets also listed. Changed javadoc mentions also as of which version does Spring bundle two MultipartResolver implementations. Issue: SPR-5984
|
thanks |
|
@rstoyanchev You're welcome. it's my pleasure. You've forgotten to close/resolve the ticket in JIRA (SPR-5984). Affected version should be changed there to 3.1 |
rwinch
pushed a commit
to rwinch/spring-framework
that referenced
this pull request
Jun 20, 2016
Flux and Mono are used both for implementation and exposed at API level to express 1 versus N semantic and to provide default Rx operators: - Flux<T> for multiple values Publisher (issue spring-projects#48) - Mono<T> for single value Publisher (issue spring-projects#50) - Mono<Void> for Publisher with no value (issue spring-projects#49)
rwinch
pushed a commit
to rwinch/spring-framework
that referenced
this pull request
Jul 13, 2016
Flux and Mono are used both for implementation and exposed at API level to express 1 versus N semantic and to provide default Rx operators: - Flux<T> for multiple values Publisher (issue spring-projects#48) - Mono<T> for single value Publisher (issue spring-projects#50) - Mono<Void> for Publisher with no value (issue spring-projects#49)
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.
Before this fix MultipartResolver javadoc mentioned that there is only
one concrete implementation included in Spring. This was true as of
Spring 2.5 but Spring 3.1 added another one, Servlet 3.0 Part API based
implementation.
This fix changes MultipartResolver javadoc so that the other one,
StandardServletMultipartResolver implementation, gets also listed.
Changed javadoc mentions also as of which version does Spring bundle
two MultipartResolver implementations.
Issue: SPR-5984
I have signed and agree to the terms of SpringSource Individual Contributor License Agreement.