Transformation authoring Release Notes

(C) Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM(R) Corp.

Contents

1.0 Known problems and workarounds
   1.1 UML Metamodel not Automatically Added to Model-to-Model Mappings
   1.2 Transformations to/from Filtered Properties May Appear Corrupted in the Mapping Editor
   1.3 Delete of Last (Only) Reference in a Mapping File to a Model Causes Drop of Model from Mapping File

1.0 Known problems and workarounds

1.1 UML Metamodel not Automatically Added to Model-to-Model Mappings

If transformations that input or output UML models are to be generated then the UML metamodel must be added as a root input and/or output of the mapping specification.  The addition of a UML profile to the mapping specification does not automatically add the UML metamodel too.  The UML metamodel can be added via the Add Model buttons available in the Model-to-Model Transformation Mapping Wizards and Editor.


1.2 Transformations to/from Filtered Properties May Appear Corrupted in the Mapping Editor

If a user switches feature filtering from "Basic" to either "Intermediate" or "Advanced" mode, creates mappings, and then switches back to "Basic" filter mode then some of the mapping endpoints might not be visible any longer and consequently the mapping connectors may seem to now have ends that don't connect to anything.  This is only a presentation issue; it does not affect the mappings or the transformation source code generated from those mappings.  The presentation can be corrected by switching back to the filter mode that was in effect when the mappings were created.

 

1.3 Delete of Last (Only) Reference in a Mapping File to a Model Causes Drop of Model from Mapping File

When a mapping file no longer contains any mappings that specify elements from some particular model as mapping inputs (outputs) then that model is "dropped" from the mapping file.  The check for unused models is made whenever a mapping input or output is deleted.  Separate lists are maintained in the mapping file for inputs and outputs.  Once a model has been "dropped" then it must be re-added (via the Add Model buttons in the Mapping Editor) before elements from that model can again be specified as mapping inputs (outputs).