0Pricing
Clean Architecture & Design Patterns in Practice · 课时

模板方法与状态模式

使用模板方法定义算法骨架，并通过状态模式让对象改变行为。

模板方法与状态模式 是 CoddyKit 上的免费 Clean Architecture & Design Patterns in Practice 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Clean Architecture & Design Patterns in Practice 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Clean Architecture & Design Patterns in Practice 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Behavioral Patterns Focus

Welcome back! In this lesson, we'll dive into two powerful behavioral design patterns: the Template Method and the State patterns.

These patterns help manage algorithms and object behavior in flexible ways, making your code easier to extend and maintain.

What is Template Method?

The Template Method pattern defines the skeleton of an algorithm in an operation, deferring some steps to subclasses.

It lets subclasses redefine certain steps of an algorithm without changing the algorithm's overall structure.

Algorithm Skeleton

Imagine a recipe with fixed steps, but some ingredients or cooking times can vary. The core "how-to" is set, but details are flexible.

  • An abstract class defines the overall algorithm with a final "template method."
  • This method calls a series of primitive operations (abstract methods) that subclasses must implement.
  • It can also include concrete methods (shared steps) and hook methods (optional steps).

Template Method in Action

Let's consider making beverages. Both coffee and tea require boiling water and pouring into a cup. But brewing and adding condiments differ.

The Template Method allows us to define the common steps once, while allowing specific beverage classes to customize their unique steps.

Beverage Maker Example

Here's how we can implement a generic BeverageMaker using the Template Method. Notice the prepareBeverage() method is final, fixing the algorithm.

public abstract class BeverageMaker {

  // The template method - defines the algorithm's skeleton
  public final void prepareBeverage() {
    boilWater();
    brew();
    pourInCup();
    addCondiments();
  }

  // Common steps
  private void boilWater() {
    System.out.println("Boiling water");
  }

  private void pourInCup() {
    System.out.println("Pouring into cup");
  }

  // Abstract steps - must be implemented by subclasses
  protected abstract void brew();
  protected abstract void addCondiments();
}

public class CoffeeMaker extends BeverageMaker {
  @Override
  protected void brew() {
    System.out.println("Dripping coffee through filter");
  }

  @Override
  protected void addCondiments() {
    System.out.println("Adding sugar and milk");
  }
}

public class TeaMaker extends BeverageMaker {
  @Override
  protected void brew() {
    System.out.println("Steeping the tea bag");
  }

  @Override
  protected void addCondiments() {
    System.out.println("Adding lemon");
  }
}

public class Main {
  public static void main(String[] args) {
    System.out.println("--- Making Coffee ---");
    BeverageMaker coffee = new CoffeeMaker();
    coffee.prepareBeverage();

    System.out.println("\n--- Making Tea ---");
    BeverageMaker tea = new TeaMaker();
    tea.prepareBeverage();
  }
}

What is the State Pattern?

The State pattern allows an object to alter its behavior when its internal state changes. It appears as if the object has changed its class.

Instead of using many if/else or switch statements, you encapsulate each state's behavior into a separate class.

Context and States

Think of a traffic light. Its behavior (what light is active) changes based on its current state (Red, Yellow, Green).

  • The Context class holds a reference to a State object and delegates state-specific behavior to it.
  • The State Interface declares methods for state-specific behaviors.
  • Concrete State classes implement the State Interface, providing behavior for a particular state.

Traffic Light States

A TrafficLight object doesn't have complex logic itself. Instead, it holds a reference to its current LightState (e.g., RedLightState, GreenLightState).

When an event occurs (like a timer tick), the TrafficLight delegates the action to its current LightState object, which then handles the transition to the next state.

Traffic Light Simulation

Here’s a simple traffic light simulation using the State pattern. The TrafficLight context changes its internal LightState object, which dictates its behavior.

// State Interface
interface LightState {
  void handleRequest(TrafficLight light);
  String getStateName();
}

// Concrete State: Red Light
class RedLightState implements LightState {
  @Override
  public void handleRequest(TrafficLight light) {
    System.out.println("Red light: STOP!");
    light.setState(new GreenLightState()); // Transition to Green
  }

  @Override
  public String getStateName() {
    return "Red";
  }
}

// Concrete State: Green Light
class GreenLightState implements LightState {
  @Override
  public void handleRequest(TrafficLight light) {
    System.out.println("Green light: GO!");
    light.setState(new YellowLightState()); // Transition to Yellow
  }

  @Override
  public String getStateName() {
    return "Green";
  }
}

// Concrete State: Yellow Light
class YellowLightState implements LightState {
  @Override
  public void handleRequest(TrafficLight light) {
    System.out.println("Yellow light: CAUTION!");
    light.setState(new RedLightState()); // Transition to Red
  }

  @Override
  public String getStateName() {
    return "Yellow";
  }
}

// Context
class TrafficLight {
  private LightState currentState;

  public TrafficLight() {
    // Initial state
    this.currentState = new RedLightState();
  }

  public void setState(LightState state) {
    this.currentState = state;
  }

  public void change() {
    System.out.print("Current state: " + currentState.getStateName() + " -> ");
    currentState.handleRequest(this);
  }
}

public class Main {
  public static void main(String[] args) {
    TrafficLight light = new TrafficLight();

    // Simulate light changes
    light.change(); // Red -> Green
    light.change(); // Green -> Yellow
    light.change(); // Yellow -> Red
    light.change(); // Red -> Green
  }
}

Pattern Identification

You are designing a document processing system where different document types (PDF, DOCX, TXT) share a common conversion process to HTML, but each has unique steps for parsing its content.

Which design pattern would best suit defining the overall conversion process while allowing specific parsing steps to vary?

Summary of Patterns

Great job! You've learned about two powerful behavioral patterns:

  • The Template Method pattern allows you to define a fixed algorithm structure while letting subclasses implement specific steps.
  • The State Pattern enables an object to change its behavior based on its internal state, encapsulating state-specific logic into separate classes.

These patterns boost flexibility and maintainability in your designs!

常见问题解答

「模板方法与状态模式」课时是免费的吗？

是的 — 「模板方法与状态模式」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Clean Architecture & Design Patterns in Practice 课程的其余内容，请升级到 CoddyKit PRO。 Clean Architecture & Design Patterns in Practice 课程共包含 4 节课。

「模板方法与状态模式」这节课中我会学到什么？

使用模板方法定义算法骨架，并通过状态模式让对象改变行为。 你通过在浏览器中直接运行的动手代码来练习 Clean Architecture & Design Patterns in Practice，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Clean Architecture & Design Patterns in Practice 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Clean Architecture & Design Patterns in Practice 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。

「模板方法与状态模式」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Clean Architecture & Design Patterns in Practice 课中编写并运行代码吗？

能。每节 Clean Architecture & Design Patterns in Practice 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 观察者与策略模式
  2. 命令与迭代器模式
  3. 模板方法与状态模式
  4. 中介者模式与责任链模式
← 返回 Clean Architecture & Design Patterns in Practice