You are right, I missed the point here... need more coffee.
Just checked collections JavaDocs, and indeed in 2.1
IteratorUtils.singletonIterator returms Iterator, while in 3.0 it
returns a subclass - ResettableIterator. So much for backwards
compatibility....
Maybe we should rollback to 2.1... Shouldn't be a big deal. Anyone
other opinion on that?
Andrus
On Mar 9, 2004, at 11:40 AM, Mike Kienenberger wrote:
>> On Mar 9, 2004, at 5:08 AM, Tore Halset wrote:
>>> I got this error when running cayenne-1.0.6 with
>>> commons-collections-3.0:
>>> java.lang.NoSuchMethodError:
>>> org.apache.commons.collections.IteratorUtils.singletonIterator(Ljava/
>>> lang/Object;)Ljava/util/Iterator;
>>> at
>>> org.objectstyle.cayenne.map.ObjAttribute.getDbPathIterator(ObjAttribu
>>> te
>>> .java:140)
>
> Andrus Adamchik <andru..bjectstyle.org> wrote:
>> This is expected. 1.0.6 is "stable" release after all, and we didn't
>> upgrade any libraries.
>
> The claim was that Collections 3.0 should be backwards-compatible to
> Collections 2.1. Why would it be expected that things would break if
> Tore
> upgraded from 2.1 to 3.0? I'd say it's a sign it's not
> backwards-compatible.
>
> -Mike
>
This archive was generated by hypermail 2.0.0 : Tue Mar 09 2004 - 11:47:17 EST