Extending object-oriented languages with backward error recovery integrated support

Invariant Implementation for Domain Models Applying Incremental OCL Techniques

“…The generated code is able to detect those potentially affecting events (what object) which combined with the delayed checking (when) and the transformed invariants translated to executable code (how) is a key difference with all DbC-like implementations for the specific case of programs built around the domain model pattern. The integration with atomicity contexts such as Reconstructors [5] or Hibernate [6] solves the problem of restoring the model to a previous state (what to do), although that integration is not mandatory; the generated code could work without that capability. As we can conclude from results section the efficiency is quite good.…”

“…Ideally this consistence integrity checking will be done in combination with some kind of atomicity handling context able to restore the model to its previous state. The tool currently integrates with Reconstructors [5], and with the Hibernate ORM [6]. The design would easily integrate also software transactional memory solutions [7,8].…”

“…There are many works on this topic. Some applies backward error recovery techniques (BER) that provide Atomicity, that is the case of Reconstructors [5]. With that property in place, programmers can assume that modifications are done in an all-or-nothing way.…”

Handling exceptions in programs with hidden concurrency: New challenges for old solutions

“…On a stable state, it would be possible to execute the error-recovery code defined by the programmer. Inspiration can come from the work of Lanvin et all [6], who proposed the concept of reconstructor: a counter-action for each operation that can take the program from the state left by that operation to the state it was in before. Having this undo semantics for all methods in a program it is possible to revert to a previous state.…”