Achim,

The classes in 2nd-level packages (like in org.apache.commons.collections.map) are 'decorators'. They are not interfaces (like MultiMap), and not self-contained implementations (like MultiHashMap). Most decorators are actually exposed as methods of MapUtils class, so an ordinary user does not need to worry about 2nd-level packages at all, just import org.apache.commons.collections.* to get MultiMap, MultiHashMap, MapUtils and almost 98.3% of the functionality of commons-collections.

Probably, these 2nd-level packages should be documented separately, to avoid confusion.

--
Andrei Polushin

Achim Westermann writes:
Thanks Henning,

I did not find it because I searched in the org.apache.commons.collections.map package. I knew the shifted semantics of a multimap but after all it is still a map. Why isn't it put under the package mentioned above? Wouldn't it be a good idea?

kind regards,

Achim

Henning P. Schmiedehausen wrote:
Achim Westermann <[EMAIL PROTECTED]> writes:
Hi list users,

As a newbie to commons collection I am searching for a MultiMap: A Map with add (another value to key) and set (replace all old values for key) operations that allows mapping multiple values to a single key. I just found a map with multiple keys for identical values... A I blind?

http://jakarta.apache.org/commons/collections/apidocs-COLLECTIONS_3_1/org/apache/commons/collections/MultiMap.html http://jakarta.apache.org/commons/collections/apidocs-COLLECTIONS_3_1/org/apache/commons/collections/MultiHashMap.html
--- cut ---
A MultiMap is a Map with slightly different semantics. Putting a value
into the map will add the value to a Collection at that key. Getting a
value will return a Collection, holding all the values put to that
key.
--- cut ---

    Best regards
        Henning

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to