EMF Transaction

Primary tabs

The transaction component provides the following capabilities.
 

  1. Multi-threading - Supports a protocol for clients to read and write EMF models on multiple threads.
  2. Model Integrity - Semantic integrity is ensured by automatic validation to detect invalid changes and semantic procedures to proactively maintain correctness of semantic dependencies.
  3. Batched Events - Clients are notified of groups of related changes in batches, rather than as a stream of EMF notifications. In particular, this allows applications to analyze change sets in their entirety.
  4. Undo/Redo - For a simplified programming model, the API automatically tracks changes applied to models without the need for client code to use EMF edit Commands. These changes are encapsulated in transactions/operations that can undo and redo themselves.
  5. Editing Domain - Support cooperative editing of models by multiple editors/applications. EMF resources can be shared amongst different editing domains.
  6. Eclipse Workspace - The API provides traceability between EMF resources and workspace resources. Multi-threaded access is coordinated via the Eclipse jobs API and its integration with the workspace.
  7. Eclipse Operations - The API supports the Eclipse operation history as an undo stack for undo/redo of resource changes. The API provides a framework for undoable operations that automatically capture undo/redo information, which can be interleaved on the same history with dependent operations that do not modify the EMF model.

 

This project is part of Mars, Luna, Kepler, Juno, Indigo, Helios, Galileo, and Ganymede.
Latest Releases: 

From December 21st, 2014 to June 25th, 2015

NameDateReview
1.9.02015-06-25
1.8.02014-06-25Review
1.7.02013-06-25Review
1.6.02012-06-24Review
1.5.12011-09-24
1.5.02011-06-24Review
Active Member Companies: 
Member companies supporting this project over the last three months.
Commit Activity: 
Commits on this project (last 12 months).