refs 2653

refs 2646

refs 2646

- This will be performed by the IElementCompositorService that is called from createNewSourceDropContext().
- Doing it here already, will trigger an expensive check for duplicate IDs when the ID assignment is issued for the second time from the IElementCompositorService
refs 2759

- I.e., do this for each specification instead of the "contained" model element. Since
"contained" might already have an any, this would trigger an expensive algorithm to
check if there are duplicated IDs.
refs 2759

- getReferencingResourceURIs(): Load side-car model resources via ResourceSet.getResource. This has the advantage that custom resource factories will be considered

- Performed some refactoring (no functional change) and added documentation
refs 2709

refs 2709

refs 2729

- prepareAnnotationEntry(): Comment out warning in case the annotation has not been instantiated yet. In the current situation, it has a performance impact on model transformations.
refs 2228

- prepareAnnotationEntry(): Emit a warning in case the annotation has not been instantiated yet. The goal is to remove the code that instantiates the annotation on the fly in the long run.
refs 2228

refs 2728

refs 2727

refs 2727

refs 2727

refs 2726

refs 2726

refs 2726

refs 2726

Ensure that IDs have been assigned to all new model elements before they are hooked to the project / resource
- Rationale
  - Model elements for which no ID has been assigned, have id 0 (which is the default value). 
  - When the new element is hooked to the resource, ResourceUtils.KernelResourceFactory.KernelXMIResource.getId() is called, which internally calls setId() to synchronize the XMI ID with the AF3 ID. In case the ID is still 0, this implicit call will corrupt the ID -> model object map (by override the mapping for key 0).
- Changes
  - ElementCompositorService: Assign IDs *before* hooking new element to the container (but of course using the container to determine the next free ID)
  - ModelElementCompositorBase: Assign IDs to newly instantiated annotations

refs 2726

refs 2726

refs 2726

refs 2726

refs 2726

refs 2726

refs 2726

refs 2726

refs 2712

- This is expected to create the right bundle URIs when the code is executed from a deployed bundle (in an RCP)

refs 2361

- Add a mechanism to create input dialogs: The action descriptor passes a map-type object that defines the expected parameters.
- Refine the container classes.
- Add an annotation action that allows to create random valued entries for a selected annotation build around an average value and the given bounds.
refs 2361

- Move the annotation and annotationEntry fields from the ColumnHandle to the AnnotationInstSpec class.
- Add a container class to the IAnnotationValueProvider that allows to specify the menu entry string and the set of elements to apply the specified action to.
- Modify the IAnnotationValueProvider and DefaultAnnotationContextActions interfaces to use the new container class.
- Adjust the GenericAnnotationView to create runnables based on the information found in the new container class.
- Simplify the "Propagate to all" annotation action.
refs 2361

refs 2709

refs 2709