You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "James Carman (JIRA)" <ji...@apache.org> on 2007/04/27 21:41:15 UTC
[jira] Commented: (COLLECTIONS-250) containsKey on MultiHashMap
seems incorrect
[ https://issues.apache.org/jira/browse/COLLECTIONS-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492379 ]
James Carman commented on COLLECTIONS-250:
------------------------------------------
The behavior has changed from what? The Map API?
> containsKey on MultiHashMap seems incorrect
> -------------------------------------------
>
> Key: COLLECTIONS-250
> URL: https://issues.apache.org/jira/browse/COLLECTIONS-250
> Project: Commons Collections
> Issue Type: Bug
> Components: Map
> Affects Versions: 3.1, 3.2
> Reporter: Nikhil G. Daddikar
> Priority: Critical
>
> MultiHashMap m = new MultiHashMap();
> m.putAll("key", Collections.EMPTY_LIST);
> System.out.println(m.containsKey("key"))
> It says false, when it should have printed true.
> The problem is that the code in MultiHashMap and even MultiValueMap has in putAll():
> if (values == null || values.size() == 0)
> {
> return false;
> }
> This means that they key is never being entered into the Map. This is causing a huge problem because the behaviour has changed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org