Difference between revisions of "Extensions.Persistence"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:OTX '''Persistence''' Extension}}[[Category:OTX-Extension]][[Category:Persistence]] | {{DISPLAYTITLE:OTX '''Persistence''' Extension}}[[Category:OTX-Extension]][[Category:Persistence]] | ||
== Classification == | == Classification == | ||
| − | {{ClassificationExtension | Persistence | Stores and retrieves runtime information | [[OtxReference#Extensions|OTX Extension]] | - | SpecifiedBy={{OtxSpec4}} | + | {{ClassificationExtension | Persistence | Stores and retrieves runtime information | [[OtxReference#Extensions|OTX Extension]] | -|-|SpecifiedBy={{OtxSpec4}} }} |
== Introduction == | == Introduction == | ||
Latest revision as of 08:56, 4 December 2019
Classification
| Name | Persistence |
| Short Description | Stores and retrieves runtime information |
| Class | OTX Extension |
| Base Extension | - |
| Pre-Conditions | - |
| Specified by | ISO 13209-4 |
Introduction
The Persistence extension is used to store and retrieve runtime information, for example information about variants of the ECU’s. ‘Persistent’ means that the value can be stored in non-volatile storage (for example a hard drive) and can be retrieved in a different process from the one that created it.
The Persistence extension is used for sessions of the same runtime system and not for exchange between different tools. The save and load activities can only be performed by the same OTX runtime application.
The Persistence extension does not provide a mechanism to delete persisted data – it is the responsibility of the runtime system to provide a mechanism (for example by a user action or a timed expiry).
Actions
| Load | |
| Save |
Exceptions
| PersistenceException | |
| PersistenceSaveException |
Checker Rules
| Persistence_Chk001 | Persistable DataTypes |
