You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/07/16 09:52:05 UTC

[jira] [Closed] (TAP5-1524) A little enhancement for multiple file upload

     [ https://issues.apache.org/jira/browse/TAP5-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jochen Kemnade closed TAP5-1524.
--------------------------------
    Resolution: Invalid

We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.

> A little enhancement for multiple file upload
> ---------------------------------------------
>
>                 Key: TAP5-1524
>                 URL: https://issues.apache.org/jira/browse/TAP5-1524
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-upload
>    Affects Versions: 5.2
>            Reporter: Vesko Georgiev
>              Labels: bulk-close-candidate
>         Attachments: tapestry-upload.zip
>
>
> Various javascript solutions for multiple file upload on the client side upload all files on one and the same key in the form. Therefore, what I did was just to change the map from <String, UploadedFile> to <String, List<UploadedFile>> in MultipartDecoder service. And driven by the least number of changes idea I added a new component called MultiUpload instead of changing the existing Upload. The new component just binds List<UploadedFile> instead of a single UploadedFile. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)