Thank you, I did as suggested, and it worked perfectly. To the framework developers: Why was the ability to set the max size removed from the default upload implementation class, and can it be put back in the class? While this workaround worked, I really don't see why it should be necessary.
Thanks again! On 12/15/05, Ben Dotte <[EMAIL PROTECTED]> wrote: > > The _maxSize variable is private unfortunately, so extending the class > isn't going to work. One trick you could use is to copy > MultipartDecoderImpl into your own project under the same package > structure and modify it there. It will use that implementation before it > uses the one in the Tapestry jar. > > The hivemind part just goes inside your module like any other > contribution: > > <?xml version="1.0"?> > <module id="..." version="..."> > <implementation > service-id="tapestry.multipart.MultipartDecoder"> > <create-instance > > class="org.apache.tapestry.multipart.MultipartDecoderImpl,maxSize=500000 > 00" model="threaded" /> > </implementation> > </module> > > Ben > > -----Original Message----- > From: Spencer Crissman [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 15, 2005 9:53 AM > To: Tapestry users > Subject: Re: Large Upload Configuration > > Not the best of news, but it does help, thanks. > > Can I just write a class that extends > org.apache.tapestry.multipart.MultipartDecoderImpl and add the setter, > and > specify my class in the implementation block that you provided, or do I > actually have to recompile the framework? (Please say the former!) > > Also, where does the <implementation> block that you provided go in the > context of the hivemodule.xml? > > That will get me up and running. Thanks for your response! > > Spencer > > On 12/15/05, Ben Dotte <[EMAIL PROTECTED]> wrote: > > > > Hi Spencer, > > > > Someone correct me if I'm wrong, but I don't think there is a way to > > override the hardcoded upload limit of 10MB in Tapestry 4 without > > overriding the framework. See > > http://issues.apache.org/jira/browse/TAPESTRY-368 or > > http://issues.apache.org/jira/browse/TAPESTRY-764 > > > > Fortunately, the fix is easy, just add a public setter for maxSize in > > MultipartDecoderImpl. Then you can configure it in your hivemodule.xml > > like so: > > > > <implementation service-id="tapestry.multipart.MultipartDecoder"> > > <create-instance > > > class="org.apache.tapestry.multipart.MultipartDecoderImpl,maxSize=500000 > > 00" model="threaded" /> > > </implementation> > > > > HTH > > > > Ben > > > > -----Original Message----- > > From: Spencer Crissman [mailto:[EMAIL PROTECTED] > > Sent: Thursday, December 15, 2005 9:17 AM > > To: Tapestry User Mailing List > > Subject: Large Upload Configuration > > > > Hello. I've updated an application from T3 to T4, and have had > success > > in > > getting everything running, but one issue is outstanding. The user > > needs to > > be able to upload large files, and I can no longer find where to set > > this > > property. In T3, the following was used in the .application file: > > > > <extension name="org.apache.tapestry.multipart-decoder" > > > > class="org.apache.tapestry.multipart.DefaultMultipartDecoder" > > > > > <configure property-name="maxSize" type="double" > > value="50000000" /> > > </extension> > > > > Where has that moved to? I'm sorry if this has come up, but all the > > references I have found on the web have dealt with this in T3 rather > > than > > T4. > > > > Thanks for the direction, > > > > Spencer > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
