Part 5 Transaction Agent Framework
This section discusses the recommended approach to persisting objects using the Jade Platform and it provides examples of a Transaction Agent Framework (TAF) that you can use in your own applications.
By the end of this section, you should be able to implement all create, update, and delete functionality using a TAF in your own Jade applications.
The code examples shown in this section are written using the 22.0.01 release version of the Jade Platform. (Code example images enclosed in a solid (unbroken) border indicate a complete Jade method, whereas a code example enclosed in a jagged (broken) border indicates a code fragment.)
The following table lists the acronyms (pronounced as a word), initialisms (pronounced as a series of letters that are abbreviations derived from the letters of the words they represent), and terms used in this section.
| Entity | Description |
|---|---|
| CRUD | Create, Read, Update, and Delete. |
| TA | Transaction Agent. |
| TAF | Transaction Agent Framework. |
| TI | Transaction Implementor. |
| UML | Unified Modeling Language. |
| Modify | Targeted update that sets specific properties on an object. |
| Persistent object | Object that exists in the database. Also referred to as persistent storage. |
| Subordinate object |
Child object referenced in a parent object; for example, an Invoice can contain a reference to a Customer object and can also create its own instance of an Address object to store the shipping address. |
| Transaction Agent | Class responsible for persisting an object. |
For details about the Transaction Agent Framework (TAF), see the following subsections.
2022.0.01 and higher

