TypeDiscoverer should not consider types implementing Iterable<…> collection like [DATACMNS-167]

[spring-projects-issues]

Oliver Drotbohm opened DATACMNS-167 and commented

It's common to have wrapper classes around collections that implement Iterable to still allow iterating over the collection but also add additional information about the collection. Currently these classes are considered collection like and thus handled like a collection in the mapping sub-system. We should only consider a type a collection like type it if is either Iterable or assignable to Collection

---

Affects: 1.3 RC1

Referenced from: commits aec655a

[nexx512]

This however leads to Issues with custom List implementations that don't want to Implement Collection but do implement Iterable. One candidate would be the lists in vavr 1.0.0 and up.
This will probably break vavr support in upcoming versions in combination with spring-data-mongo.

If there is a wrapper class that wraps many elements I would think this class is collection like. Does this cause problems with the mapping sub-system?

[nexx512]

I think i found a better solution and provided it with pull request #2511.