[ http://issues.apache.org/jira/browse/MYFACES-655?page=all ]
Oliver Rossmueller resolved MYFACES-655:
----------------------------------------
Resolution: Won't Fix
It's valid behaviour for a Map not to implement putAll() and clear() but to
throw UnsupportedOperationException instead. The MyFaces impl follows the JSF
RI in this aspect to comply with the spec.
> 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
>
> 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
