[
https://issues.apache.org/jira/browse/TRINIDAD-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711140#action_12711140
]
Mark Yvanovich commented on TRINIDAD-1464:
------------------------------------------
Rather than nesting the config settings, I think a flat approach for the names
will be easier to implement.
<uploaded-file-max-memory>#{bean.blah}</uploaded-file-max-memory>
<uploaded-file-max-disc-space>#{bean.blub}</uploaded-file-max-disc-space>
<uploaded-file-temp-dir>#{bean.fooDir}</uploaded-file-temp-dir>
> 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.
