[
https://issues.apache.org/jira/browse/TAP5-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade updated TAP5-1524:
---------------------------------
Labels: bulk-close-candidate (was: )
This issue has been last updated more than a year ago, has no assignee, affects
an old version of Tapestry that is not actively developed anymore, and is
therefore prone to be bulk-closed in the near future.
If the issue still persists with the most recent development preview of
Tapestry (5.4-beta-26, available from Maven Central), please update it as soon
as possible. In the case of a feature request, please discuss it with the
Tapestry developer community on the d...@tapestry.apache.org mailing list first.
> 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)
