Design patterns: elements of reusable object-oriented software
Design patterns: elements of reusable object-oriented software
Doing hard time: developing real-time systems with UML, objects, frameworks, and patterns
Doing hard time: developing real-time systems with UML, objects, frameworks, and patterns
Patterns of Enterprise Application Architecture
Patterns of Enterprise Application Architecture
Agile Database Techniques: Effective Strategies for the Agile Software Developer
Agile Database Techniques: Effective Strategies for the Agile Software Developer
Core J2EE Patterns (Core Design Series): Best Practices and Design Strategies
Core J2EE Patterns (Core Design Series): Best Practices and Design Strategies
Java(TM) EE 5 Tutorial, The (3rd Edition) (The Java Series)
Java(TM) EE 5 Tutorial, The (3rd Edition) (The Java Series)
Spring in action
Microsoft .NET: Architecting Applications for the Enterprise
Microsoft .NET: Architecting Applications for the Enterprise
EJB 3 in Action
Fundamentals of Database Systems
Fundamentals of Database Systems
Hi-index | 0.00 |
Finite State Machines (FSM) provide a powerful way to describe dynamic behavior of systems and components. Implementations of FSM in Object-Oriented (OO) languages have been widely studied since the classical State Pattern has been introduced. Various design patterns were derived from the State Pattern, but all of the focus on object's behavior. This paper describes the Persistent State Pattern, an extension to the State Pattern for persistent data. The Persistent State Pattern integrates transaction management with classical and enterprise design patterns. It can be used with OO databases and relational databases, and it can also be incorporated by an object-relation mapping framework. We show how the Persistent State Pattern may be useful for model or event driven development.