JoinedIterator remove method broken
Description
The remove() method will always delegate to the first iterator.
public void test() {
ArrayList<Integer> list1 = new ArrayList<Integer>();
ArrayList<Integer> list2 = new ArrayList<Integer>();
list1.add(1);
list1.add(2);
list2.add(3);
list2.add(4);
JoinedIterator i = new JoinedIterator(list1.iterator(),list2.iterator());
while (i.hasNext()) {
int item = (Integer)i.next();
if (item == 3) {
i.remove();
}
}
assertEquals(2, list1.size());
assertEquals(1, list2.size());
}
Environment
N/A
Activity
In an effort to clean up, in bulk, tickets that are most likely out of date, we're transitioning all ORM 3 tickets to an "Awaiting Test Case" state. Please see http://in.relation.to/Bloggers/HibernateORMJIRAPoliciesAndCleanUpTactics for more information.
If this is still a legitimate bug in ORM 4, please provide either a test case that reproduces it or enough detail (entities, mappings, snippets, etc.) to show that it still fails on 4. If nothing is received within 3 months or so, we'll be automatically closing them.
Thank you!
Bulk rejecting stale issues. If this is still a legitimate issue on ORM 4, feel free to comment and attach a test case. I'll address responses case-by-case. Thanks!
