myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthias Weßendorf (JIRA) <>
Subject [jira] Commented: (TRINIDAD-1464) max upload size cannot be reconfigured after app is deployed
Date Fri, 01 May 2009 11:27:30 GMT


Matthias Weßendorf commented on TRINIDAD-1464:

Generally, the "problem" is that the UploadProcessor is shared across sessions (application
and therefore it could be possible that user #1 (for what ever reason) changes the max-upload
to 1 kilobyte...
(in case the application developer would create such a stupid user-interface...)

Generally the usage of such a feature would only make sense in an admin-type GUI....

> max upload size cannot be reconfigured after app is deployed
> ------------------------------------------------------------
>                 Key: TRINIDAD-1464
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: New Feature
>    Affects Versions:  1.2.11-core
>            Reporter: Matthias Weßendorf
>            Assignee: Matthias Weßendorf
> Currently the only way to configure the max upload size it to set context
> parameters in web.xml. Some container do not provide any support for changing
> web.xml during or after deployment...
> Applications needs to be able to change the max upload size after deployment.
> This could be done by providing an implementation of
> org.apache.myfaces.trinidad.webapp.UploadedFileProcessor. However that 
> would be a relatively simple variation on
> org.apache.myfaces.trinidadinternal.config.upload.UploadedFileProcessorImpl 
> We need to find a good way to dynamically change those configuration settings

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message