Weaver: operation weaving inconsistent when multi mapping

[Cécile Camillieri]

When you multi map an operation, message views are not woven correctly for operations with no message view.

In the example below I reused Observed and mapped 'modify' to different operations.

• In the first case (above). I map it to operations with no message view defined. In the woven result, only the first operation was woven.
• In the second case (below). I map it to the same to operations, plus an operation which had a message view. The result is that only the one with the message view is woven. The first mapping is not woven anymore.

In this particular case of course we need to have a message view for the operations mapped to modify, so in the end it would not be a real problem.

A similar thing happens when you multi map classes, for example if you map Observer to a second class, operations like startObserving will be copied for the second class, but they will not have the message view defined.

This may be something we want to fix only when we implement instantiation cardinalities into TouchCORE.