Naked Objects
By Richard Pawson and Robert Matthews

Building a multi-user system

Maintaining transactional integrity

If your persistence mechanism has the ability to manage transactions (as do most relational databases, for example), then Naked Objects can make full use of this. By default, every explicit user action such as selecting an action from a pop-up menu, changing a field, or dragging and dropping an object, is assumed to be an atomic transaction even if that action triggers changes to multiple fields or other objects. When each action occurs, the framework automatically sends a 'start transaction' message to the object store, and concludes it with an 'end transaction'.