[
https://issues.apache.org/jira/browse/TRINIDAD-1843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated TRINIDAD-1843:
-----------------------------------------
Status: Resolved (was: Patch Available)
Assignee: Matthias Weßendorf
Fix Version/s: 2.0.0.3-core
Resolution: Fixed
> Need to feedback failures for users when a file processor in chain fails
> ------------------------------------------------------------------------
>
> Key: TRINIDAD-1843
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1843
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Components
> Affects Versions: 2.0.0.3-core
> Reporter: Prakash Udupa
> Assignee: Matthias Weßendorf
> Fix For: 2.0.0.3-core
>
> Attachments: FileUploadFailureMessageSupport_1843_Trin_trunk.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> Through JIRA 1757 (https://issues.apache.org/jira/browse/TRINIDAD-1757, we
> supported chaining of uploaded file processors.
> There are two means for file upload processors to convey failures.
> 1. UploadedFileProcessor.processFile() implementations can throw IOException.
> 2. UploadedFile.getOpaqueData() implementation can convey more information
> about error.
> Example of failures could be no space in disk, unacceptable end of line
> markers, virus etc. Some of these failures need to be notified to users, and
> currently there is no good mechanism to show this to end users. We log #1,
> and we do not interpret #2. The File upload happens before the JSF lifecycle
> kicks in, so we cannot raise faces exceptions or use faces message.
> This JIRA issue is to track providing some means for the uploaded file
> processors to be able to propagate failure message to end users.
> I'm working on a solution and will provide patch soon.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
