Skip to main content

AMW - 20060717 - New and Noteworthy

New release / commit with many changes in the Model Weaver.

  • In the first page of the wizard, it is now possible to load KM3 metamodel extensions or a complete weaving metamodel conforming to Ecore.
  • The default extension for weaving models changed to .amw.
    Weaving models with .ecore extension are still compatible.
  • The weaving models now support metamodels by URI. In the third page of the wizard, the URIs can be direclty typed into the corresponding text fields.
  • The woven models are not identified by their URIs anymore. There is a new identifier adapter that calculates the relative path of the woven models. (class ResourceIdentifierAdapter).
  • Now the base extension plugin has two implementation of "woven panels" (there is no need to change the code anymore).

    • The first implementation (DefaultWovenModelPanel) supports generic IDs (XPointer).
    • The second one (WovenPanelXMI) supports XMI IDs. The panels must be choosen following the corresponding WModelRef extension (ModelRef or ModelRefXMI).
  • There is a new identifier adapter available (MergeIdentifierAdapter). It calculates the ID of an element by using the containment tree (similar to XPointer).
  • Every weaving model has a a metadata file associated. In the previous versions this file was hidden from the users.
    Now this file is available at the same folder of the weaving model, with the name "weavingmodel-name".prop.
    This file can be modified to change the model paths and the visualization settings.

The changes are available in the latest version of the CVS. The previou version (for compatibility issues) was tagged with name build20060713

The previous examples will continue to work after these modifications. The only requirement is to re-generate the metadata file as usual.

Back to the top