mirror of
https://github.com/tiennm99/java-design-patterns.git
synced 2026-05-14 20:58:35 +00:00
175 lines
5.2 KiB
Markdown
175 lines
5.2 KiB
Markdown
---
|
|
title: Iterator
|
|
category: Behavioral
|
|
language: en
|
|
tag:
|
|
- Data access
|
|
- Data transformation
|
|
- Decoupling
|
|
- Gang of Four
|
|
- Object composition
|
|
- Polymorphism
|
|
---
|
|
|
|
## Also known as
|
|
|
|
* Cursor
|
|
|
|
## Intent
|
|
|
|
The Iterator pattern provides a way to access elements of an aggregate object sequentially without exposing its underlying representation.
|
|
|
|
## Explanation
|
|
|
|
Real-world example
|
|
|
|
> Imagine visiting a library with a vast collection of books organized in different sections such as fiction, non-fiction, science, etc. Instead of searching through every shelf yourself, the librarian provides you with a specific guidebook or a digital catalog for each section. This guidebook acts as an "iterator," allowing you to go through the books section by section, or even skip to specific types of books, without needing to know how the books are organized on the shelves. Each guidebook handles the traversal through its section, providing a consistent and efficient way to access the books, much like how the Iterator design pattern offers a uniform method to traverse different data structures in a software application.
|
|
|
|
In plain words
|
|
|
|
> The Iterator design pattern provides a way to access the elements of a collection sequentially without exposing the underlying structure of the collection.
|
|
|
|
Wikipedia says
|
|
|
|
> In object-oriented programming, the iterator pattern is a design pattern in which an iterator is used to traverse a container and access the container's elements.
|
|
|
|
**Programmatic Example**
|
|
|
|
The main class in our example is the `TreasureChest` that contains items.
|
|
|
|
```java
|
|
public class TreasureChest {
|
|
|
|
private final List<Item> items;
|
|
|
|
public TreasureChest() {
|
|
items = List.of(
|
|
new Item(ItemType.POTION, "Potion of courage"),
|
|
new Item(ItemType.RING, "Ring of shadows"),
|
|
new Item(ItemType.POTION, "Potion of wisdom"),
|
|
new Item(ItemType.POTION, "Potion of blood"),
|
|
new Item(ItemType.WEAPON, "Sword of silver +1"),
|
|
new Item(ItemType.POTION, "Potion of rust"),
|
|
new Item(ItemType.POTION, "Potion of healing"),
|
|
new Item(ItemType.RING, "Ring of armor"),
|
|
new Item(ItemType.WEAPON, "Steel halberd"),
|
|
new Item(ItemType.WEAPON, "Dagger of poison"));
|
|
}
|
|
|
|
public Iterator<Item> iterator(ItemType itemType) {
|
|
return new TreasureChestItemIterator(this, itemType);
|
|
}
|
|
|
|
public List<Item> getItems() {
|
|
return new ArrayList<>(items);
|
|
}
|
|
}
|
|
```
|
|
|
|
Here's the `Item` class:
|
|
|
|
```java
|
|
public class Item {
|
|
|
|
private ItemType type;
|
|
private final String name;
|
|
|
|
public Item(ItemType type, String name) {
|
|
this.setType(type);
|
|
this.name = name;
|
|
}
|
|
|
|
@Override
|
|
public String toString() {
|
|
return name;
|
|
}
|
|
|
|
public ItemType getType() {
|
|
return type;
|
|
}
|
|
|
|
public final void setType(ItemType type) {
|
|
this.type = type;
|
|
}
|
|
}
|
|
|
|
public enum ItemType {
|
|
|
|
ANY, WEAPON, RING, POTION
|
|
|
|
}
|
|
```
|
|
|
|
The `Iterator` interface is extremely simple.
|
|
|
|
```java
|
|
public interface Iterator<T> {
|
|
|
|
boolean hasNext();
|
|
|
|
T next();
|
|
}
|
|
```
|
|
|
|
In the following example, we iterate through the ring-type items found in the chest.
|
|
|
|
```java
|
|
var itemIterator = TREASURE_CHEST.iterator(ItemType.RING);
|
|
while (itemIterator.hasNext()) {
|
|
LOGGER.info(itemIterator.next().toString());
|
|
}
|
|
```
|
|
|
|
Program output:
|
|
|
|
```java
|
|
Ring of shadows
|
|
Ring of armor
|
|
```
|
|
|
|
## Class diagram
|
|
|
|

|
|
|
|
## Applicability
|
|
|
|
Use the Iterator pattern
|
|
|
|
* To access an aggregate object's contents without exposing its internal representation.
|
|
* To support multiple traversals of aggregate objects.
|
|
* To provide a uniform interface for traversing different aggregate structures.
|
|
|
|
## Tutorials
|
|
|
|
* [How to Use Iterator?](http://www.tutorialspoint.com/java/java_using_iterator.htm)
|
|
|
|
## Known uses
|
|
|
|
* Java Collections Framework utilizes iterators extensively to allow different ways to traverse through collections.
|
|
* Databases often use iterators to navigate through data records fetched through SQL queries.
|
|
* [java.util.Iterator](http://docs.oracle.com/javase/8/docs/api/java/util/Iterator.html)
|
|
* [java.util.Enumeration](http://docs.oracle.com/javase/8/docs/api/java/util/Enumeration.html)
|
|
|
|
## Consequences
|
|
|
|
Benefits:
|
|
|
|
* Reduces the coupling between data structures and algorithms used for iteration.
|
|
* Provides a uniform interface for iterating over various types of data structures, enhancing code reusability and flexibility.
|
|
|
|
Trade-offs:
|
|
|
|
* Overhead of using an iterator object may slightly reduce performance compared to direct traversal methods.
|
|
* Complex aggregate structures may require complex iterators that can be difficult to manage or extend.
|
|
|
|
## Related Patterns
|
|
|
|
* [Composite](https://java-design-patterns.com/patterns/composite/): Iterators are often used to traverse Composite trees.
|
|
* [Factory Method](https://java-design-patterns.com/patterns/factory-method/): Used to create appropriate iterators for different data structures.
|
|
* [Visitor](https://java-design-patterns.com/patterns/visitor/): Can be used with Iterator to apply operations over elements of an object structure.
|
|
|
|
## Credits
|
|
|
|
* [Design Patterns: Elements of Reusable Object-Oriented Software](https://amzn.to/3w0pvKI)
|
|
* [Head First Design Patterns: Building Extensible and Maintainable Object-Oriented Software](https://amzn.to/49NGldq)
|