Yes, that's correct. The docs need to be updated. The
tapestry.multipart.MultipartDecoder service id was changed to
tapestry.multipart.ServletMultipartDecoder, probably to help
differentiate it from the
tapestry.portlet.multipart.PortletMultipartDecoder service id.
An easy way to look up HiveMind service id's is via the HiveDoc report
on the Tapestry home page. It's in the menu under
Stanczak Group wrote:
> Seems changing it to ServletMultipartDecoder fixes it, but is the the
> correct way?
> Here's what I have in the hivemodule.xml:
> <implementation service-id="tapestry.multipart.ServletMultipartDecoder">
> model="threaded" />
> Stanczak Group wrote:
>> What's the new method to set the max file size, I can't seem to find it
>> in the docs, google, or in the code. Also if someone could point out how
>> to look in the code and find the answer it would help me in the future.
>> Here's the story. Was using 4.0 and set the maxSize like said on the
>> docs. Got message that parameter didn't exist. Looked in code to see it
>> wasn't there. Download 4.0.1 looked in code to see it was there, and it
>> was. Setup like online docs say and now get "unknown service point
>> tapestry.multipart.MultipartDecoder.". So, looked in sources again to
>> find answer, but don't know how to find it (for example in /WEB-INF,
>> didn't see the answer in tapestry.multipart.xml).