There is a list of uploaded files. You can add more files by adding them with the MultiUpload Button which is working fine for one run to upload one or multiple files.
If you use the same MultiUpload Button again, the list of files is not deleted despite the fact of using
The newly uploaded files are added to the list of the files already deleted in the run before. This list gets larger each upload and I would have to check each entry, if the file still is existing or might be new ;/
With the second upload button where I create each time of the upload a new MultiUploader it is working.
Hint
I found in the Jmix-UI a property uploadHandlerType, but the Studio complains you if you try to set this handler.
I think, there is a bug here
UPDATE
I did change MultiFileTemporaryStorageBuffer to MultiFileMemoryBuffer ( deprecated … ) and was then able in public void onUploadAllFinished(final AllFinishedEvent event) {
to assign a new Buffer
MultiFileMemoryBuffer newBuffer = new MultiFileMemoryBuffer();
upload.setReceiver(newBuffer);
so, the program is finally working, otherwise there is the same bug with this implementation too.
The Clear/Remove button doesn’t remove a successfully uploaded file from the server file system or database. It’s only removed from the file list. Remember to remove the file from the backend.
Same is applicable to the clearFileList() method.
The problem is that MultiFileReceiver doesn’t have API to clear uploaded file list. MULTI_FILE_MEMORY_BUFFER maps to Vaadin’s com.vaadin.flow.component.upload.receivers.MultiFileMemoryBuffer which we cannot “fix”. So your WA with setting a new receiver is good one.
Considering the logic of UploadProcessListView, looks like fileStorageUploadField would be more convenient. Same for the detail view.
If you’re referring to the uploadHandlerType attribute, I don’t see it described in the documentation.
It’s fully supported as it designed by Vaadin. We only provide 2 receivers and localization.
