[COLLECTIONS-424] Surprising exception by CompositeSet in a situation where CompositeCollection works fine

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2.1
• Fix Version/s: 4.0-alpha1, 4.0
• Component/s: Set

Environment

All environments

• Assignee: Unassigned
• Reporter: Michael Pradel
• Created: 23/Jul/12 09:07
• Updated: 09/Nov/14 14:31
• Resolved: 17/Mar/13 10:03

Description

We have a method that uses a CompositeCollection. Here's a simplified version of it:

void m(CompositeCollection coll)

{ coll.addComposited(new TreeBag()); }

It works fine when the argument is a CompositeCollection, but it throws an exception when the argument is a CompositeSet. E.g.:

m(new CompositeCollection()); // OK
m(new CompositeSet()); // IllegalArgumentException

Although the exception is documented in CompositeSet, this behavior is very surprising. Is there a way to have m() accept CompositeCollections without running into this exception? The only solution that comes to my mind is to dynamically check the type of 'coll' in m(), but this is a rather nasty work-around.

A better solution may be to make the genericity of CompositeCollection explicit by adding a type parameter:

class CompositeCollection<T extends Collection> {
void addComposited(T c)

{ /* .. */ }
}

class CompositeSet extends CompositeCollection<Set> {
@Override void addComposited(Set c) { /* .. */ }

}

This way, users of CompositeCollection must choose the kind of collections that can be composed and will not encounter surprises, such as the above.