📄️ TransactionManager Tutorial
The code lives under tutorials/transaction-manager. Use the QMUX or LogonManager tutorials as a client — they connect to port 10000 by default.
📄️ Context
Context is the transaction's blackboard. It flows through every participant and carries everything they need to communicate — the incoming message, the response being built, database handles, audit data, and anything else a participant wants to share with participants that run later.
📄️ TransactionParticipant
The TransactionParticipant interface is the building block of every jPOS transaction:
📄️ AbortParticipant and SendResponse
The problem with the happy path only
📄️ Groups and GroupSelector
A single flat participant chain works for simple servers. Production systems handle many message types — authorisations, reversals, network management, balance inquiries — each with a different processing pipeline. Groups and GroupSelector provide the mechanism for runtime routing between pipelines.