Keep completed flag for retained/duplicated HttpData #12576
Merged
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.
Motivation:
When you retain and duplicate a multipart HttpData, then the "isCompleted" flag is not preserved.
Example:
Using the following code:
then data.isCompleted() returns false, but duplicate.isCompleted() will return true
Modification:
retainDuplicate actually calls replace method, and when the various replace methods are calling setContent(), then after the call to setContent, the isCompleted flag will be reset to true.
The propose patch adds a new setCompleted(boolean) method in AbstractHttpData class, and then all the replace methods ensure that the setCompleted method is called after having called setContent.
Example for the replace method implemented by the MemoryFileUpload class:
Result:
The isCompleted flag is preserved in the HttpData returned by the retainedDuplicate() method, so users can check if the HttpData is partial or not.
thanks.