[jira] Commented: (TRINIDAD-1464) max upload size cannot be reconfigured after app is deployed

["Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TRINIDAD-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704509#action_12704509 ] 

Matthias Weßendorf commented on TRINIDAD-1464:
----------------------------------------------

The most simple case would be to enhance the UploadedFileProcessor, by adding some s/getConfiguration() method.
However, that causes serious problems for 3rd party implementations (fragile base class problem).

A smarter adapter would be needed...

> max upload size cannot be reconfigured after app is deployed
> ------------------------------------------------------------
>
>                 Key: TRINIDAD-1464
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-1464
>             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.