not sure if this may work with Blossom, since it was for an old Spring
MVC version (and old magnolia versions), but we already had a
MagnoliaMultipartResolver which does the bridge between Magnolia
multipart filters and Spring multipart resolvers...
Thanks, Fabrizio.
Unfortunately, I already wrote the patch (which is now attached to
BLOSSOM-11) before seeing this mail. It's almost identical to what I
wrote, so it should be a good solution. I suppose yours could work as is
even with spring 3 but I didn't try.
The only real difference is that you used the default spring multipart
wrapper (DefaultMultipartHttpServletRequest) and I created a separated
class. The default spring wrapper does the "sum" of request parameters
and multipart parameters, which is already done by Magnolia wrapper.
Nothing devastating, but I just wanted to avoid problems similar to
MAGNOLIA-3211.
Regards, Danilo.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
