[ http://issues.apache.org/jira/browse/MYFACES-655?page=comments#action_12331257 ]
Mathias Broekelmann commented on MYFACES-655: --------------------------------------------- Thanks Craig for giving some light to this. I still think there is a difference between optional an mandatory. If clear and putAll is an optional operation for a mutable map why is the tck expecting it to throw an UnsupportedOpperation? IMO this is a tck issue. > RequestMap doesn't implement putAll as it should > ------------------------------------------------ > > Key: MYFACES-655 > URL: http://issues.apache.org/jira/browse/MYFACES-655 > Project: MyFaces > Type: Bug > Versions: 1.1.0 > Reporter: Colin Sampaleanu > Assignee: Mathias Broekelmann > > The JSF description of for the ExternalContext.getRequestMap() method says: > """Return a mutable Map representing the request scope attributes for the > current application. The returned Map must implement the entire contract for > a modifiable map as described in the JavaDocs for java.util.Map. > Modifications made in the Map must cause the corresponding changes in the set > of request scope attributes.""" > yet MyFaces returns a RequestMap class which throws > UnsupportedOperationException for both the putAll() and the clear() methods. > This is a major bug which will break apps (like mine) that depend on being > able to add params via putAll(), for example. -- 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
