On 20/06/2006, at 6:04 PM, Lachlan Deck wrote:
Hi there,
On 15/06/2006, at 8:22 PM, John Larson wrote:
objectEnumerator does work. I didn't even think that that would
be a different implementation except for Iterator's remove()
method. Oh well, just trying to obey Sun's advice about the
Sorry, I was a little misleading. The Java 1.4.2 API for java.util.Enumeration says: "NOTE: The functionality of this interface is duplicated by the Iterator interface. In addition, Iterator adds an optional remove operation, and has shorter method names. New implementations should consider using
Hi there,
On 15/06/2006, at 8:22 PM, John Larson wrote:
objectEnumerator does work. I didn't even think that that would be
a different implementation except for Iterator's remove() method.
Oh well, just trying to obey Sun's advice about their Collections
framework and not have to call me
Thanks Chuck,
objectEnumerator does work. I didn't even think that that would be a
different implementation except for Iterator's remove() method. Oh
well, just trying to obey Sun's advice about their Collections
framework and not have to call methodWithAsLongANameAsPossible(). :-)
John
I can't confirm it, but I would not be surprised. Sounds like
whoever added this method neglected to fire the fault before
creating the iterator. I'll suggest using objectEnumerator()
instead of calling count().
Chuck
On Jun 14, 2006, at 7:35 PM, John Larson wrote:
Hello all,
can any
Hello all,can anyone please confirm this as a bug in WebObjects 5.3.1. When using an NSArray that is a to-many relationship from an entity, the listIterator() method returns an empty list if the NSArray has not had at least count() executed against it. The same happens when using the iterator() m
