Mappings

graphical mapping

• Only a few attributes have to be mapped ...

• and you want to document which attributes are used for the mapping.

• Use graphical mapping as long as it is well arranged (avoid crossing lines)

• Also a matter of taste

  • Pro: good graphical view including mapping rules on dependencies

  • Con: takes long time to draw, problem when re-importing classes (e.g. Salesforce WSDL)

script mapping

You have many attributes or complex mappings with rules and conversions.

When using script mapping, use a class diagram and put the script into the E2ESimpleMapping dependency

mapEqualNames

One use case could be, if the classes are given through a backend (e.g. createCustomerClass and UpdateCustomerClass which are equal but createCustomerClass has custID in addition or they are inherited from the same parent.

Be careful when using it and ask yourself: Are the attribute names of the two classes really the same and have all equal types?

mapping context

You want to map hierarchical objects.  Mapping context automatically iterates through the hierarchy defined in the class diagram.

Advantages

• external specification, therefore, can be tested externally

• changes must not always be re-compiled

• quicker?

• good scaling for big files

• good for structural mappings (deep hierarchies to flat or different hierarchies)

Disadvantages

• mapping documentation only good for those who know the XSLT syntax