Mastering Java State Machines with Enums: A Practical Guide

Preface

Many Java developers have written business logic for status changes such as order processes or leave requests, often using a status flag and a series of if statements. When the number of states grows, the code becomes unwieldy.

Instead of piling up if statements, the State pattern can be used, allowing an object to change its behavior based on its current state. However, this can introduce many state objects and dependencies.

What is a State Machine

A finite state machine (FSM) models a limited set of discrete states and the transitions between them. It defines a set of states, the events that trigger transitions, and the actions performed during those transitions.

State : The current condition of the system.

Event : An occurrence that may cause a state transition.

Action : Business logic executed when a transition occurs (e.g., writing a transaction record, updating an account balance).

Transition : The process of moving from one state to another triggered by an event.

Java Enum

Java enums, introduced in JDK 1.5, are special classes that represent a fixed set of constants. They are implemented as singletons, ensuring thread safety, and can implement interfaces and declare abstract methods that each constant overrides.

Example of a color enum (illustrated below) shows how each constant can provide its own behavior:

Practical Implementation

Consider an order delivery process with three stages: scheduling, dispatch, and receipt. The following enum defines the possible states and the logic for moving between them:

In this design, the initial state points to itself for prevState, and the final state points to itself for nextState. The order workflow can then be driven by the enum, reducing boilerplate code.

Sample code (illustrated) shows how the order transitions through the states:

A simple test demonstrates that after two transitions the order reaches the buyer, and the state changes correctly, improving maintainability.