Generic Event-B EMF extensions

Refinement

AVAILABLE IN NEXT RELEASE OF ac.soton.eventb.emf.core.extension.feature

The Rodin platform provides an extension point for contributing behaviour to the 'Refine' action. For Serialised Event-B EMF extensions, an abstract, reflective refinement contributor class is provided to simplify the task of making a refinement.

The class is ac.soton.eventb.emf.core.extension.navigator.refiner$AbstractExtensionRefiner which implements IRefinementParticipant. The class should be extended by a client plug-in and the clients class should be registered as a Refinement Participant using the relevant Rodin extension point The client class must implement the method getExtensionID() to return the relevant Extension ID string that identifies such extensions. The client class may override populateReferenceMap(Map<>) to add the EReference Features that need to be dealt with, defining which ones are back references to the corresponding abstract element.

The generic refiner class works as follows:

• All serialised extensions of the given Extension ID in the Rodin resource are loaded
• Each one is deep cloned using the Ecore copier utility
• The contents of the extension are then searched for elements that own one of the client supplied EReferences.
• For each reference, the reference is either set to reference the corresponding source abstract element or copied so that it corresponds to the abstract reference

Generator

AVAILABLE IN NEXT RELEASE OF ac.soton.eventb.emf.core.extension.feature

A framework to support the implementation of generators is provided. The framework is designed to support the generation of standard Event-B models from higher-level model extensions that are based on the Event-B EMF modelling extensions framework.

The Generator framework provides:

• A toolbar button to initiate the generation
• Generic code to remove previously generated elements
• Generic code to organise the incorporation of newly generated elements
• Utilities to aid the creation of new elements
• An abstract basis for client defined rules
• An extension point for clients to declare generators and generation rules

The client rules return generation descriptors (rather than modifying the target model directly). The framework takes care of updating the model (within the clients Transactional Editing Domain) provided the generation completes successfully. This ensures that the model is not left in an inconsistent state should the generation fail. The generation descriptors allow the client to specify where the new element should be contained and a priority which will be used to influence the placement of the new element within the containment ordering.

To define a particular generator a client should:

• Define an extension point for org.eclipse.ui.handlers to enable the generate command when the activePartID is their Editor (see Defining a generator handler)