[
http://jira.magnolia-cms.com/browse/BLOSSOM-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30118#action_30118
]
Tobias Mattsson commented on BLOSSOM-18:
----------------------------------------
Appears to have been introduced with SPR-2784
https://jira.springframework.org/browse/SPR-2784.
> BlossomMultipartRequestWrapper doesn't work with Spring 3.
> ----------------------------------------------------------
>
> Key: BLOSSOM-18
> URL: http://jira.magnolia-cms.com/browse/BLOSSOM-18
> Project: Magnolia Blossom Module
> Issue Type: Bug
> Affects Versions: 1.1.1
> Reporter: Danilo Ghirardelli
> Assignee: Tobias Mattsson
>
> BlossomMultipartRequestWrapper estends AbstractMultipartHttpServletRequest.
> In Spring 2.5.x, AbstractMultipartHttpServletRequest.setMultipartFiles has a
> parameter of type Map, but in Sping 3.0.x the parameter has been narrowed to
> type MultiValueMap, which is an extension of Map included in spring-core 3
> (and unfortunately not included in spring 2.5).
> Current BlossomMultipartRequestWrapper is passing a Map to the
> setMultipartFiles, and using Spring 3 this will cause an exception.
> Before writing a reflection nightmare to populate the right parameter, is
> there any other way to get around this? Maybe two different
> BlossomMultipartRequestWrapper compiled for specific spring versions?
> I honestly can't see a simple solution to overcome the problem, even
> upgrading the dependency to spring version would make it incompatible with
> older spring, unless MultiValueMap is copied and included in blossom release
> (which doesn't seem a good idea).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
