Managing mapping rules in model-to-model
transformation mapping projects
Mapping rules, also called mappings, specify how
to assign a value to an attribute of an output object, according to
the values of the attributes of an input object.
Creating mapping rules in mapping projects In model-to-model transformation
mapping projects, you can create mapping rules between the features
of the input and output objects in the mapping declaration; you can
also create mapping rules between the input and output objects themselves.
If the mapping declaration inherits mapping rules from another mapping
declaration, you can create rules that override the inherited mapping
rules.
Changing mapping rule types in mapping projects When you create a mapping rule
in a model-to-model-transformation mapping project, the type of mapping
rule is specified automatically in the editor area.
Refining move and submap mapping rules in mapping projects
In model-to-model transformation
mapping projects, you can refine the mapping rules that you specify
in a mapping declaration. This feature enables you to customize the
behavior of a mapping rule.
Specifying implementation code for custom mapping rules in mapping projects You can specify whether the custom
mapping rule invokes inline or external code that calculates the value
of an output property in a model-to-model transformation. You can
specify semantic refinements by using Java code
fragments or classes.
Changing the display order of mapping rules in mapping projects You can change the order in which
mapping rules are displayed. Sorting the mapping rules provides a
clearer view of the mapping rules; it does not alter the order in
which the transformation processes mapping rules.
Changing the processing order of mapping rules in mapping projects
You can change the order
in which a transformation processes mapping rules. This functionality
is useful if custom code or the order of submap invocations have dependencies
on the output that other mappings generate. The Outline view
lists the mapping rules in the order that they are processed when
you run the generated transformation code.