[
http://issues.apache.org/jira/browse/TAPESTRY-368?page=comments#action_12371289
]
Paul Ferraro commented on TAPESTRY-368:
---------------------------------------
Oops - the hivemodule.xml snippet from the previous post should read:
<implementation service-id="tapestry.multipart.ServletMultipartDecoder">
<create-instance
class="org.apache.tapestry.multipart.MultipartDecoderImpl,sizeMax=-1"
model="threaded" />
</implementation>
Sorry for any potential confusion...
> Please add setMaxSize to MultipartDecoder
> -----------------------------------------
>
> Key: TAPESTRY-368
> URL: http://issues.apache.org/jira/browse/TAPESTRY-368
> Project: Tapestry
> Type: New Feature
> Components: Framework
> Versions: 4.0
> Reporter: Gavin Mathias
> Priority: Minor
> Fix For: 4.0.1
> Attachments: tap368.txt
>
> I use the Upload component to upload files to my application. Most of those
> files are over the size limit of 10000000 hardcoded in MultipartDecoderImpl.
> Please add setMaxSize(int _maxsize) to MultipartDecoder so that I can write
> a custom Upload component that can do this:
> getDecoder().setMaxSize(30000000);
> Even nicer would be a parameter in Tapestry's Upload.jwc that can be used to
> set MaxSize.
> I was doing this in Tapestry3.0.3 by calling:
> DefaultMultipartDecoder.getSharedInstance().setMaxSize(30000000);
> in my custom component's page class.
> Thanks and Best Regards,
> Gavin
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
