Collecting all structural features contains mapped attributes

[Matthias Schoettle]

Consider (on branch WorkflowUpdate) the message view of InputQueue.create(String) in design model Input.

Actual Result:

• Double-tap on assignment statement with queueName
• Result: The selector contains both queueName and name (the latter was mapped to the former)
• Also, double-tap on assignment of message following above mentioned statement
• Same result as above

Expected Result:

The selector should not contain attributes that were mapped, e.g., name in this example.

The operation RAMEditUtil.collectStructuralFeatures should consider mapped attributes in a similar way than RAMEditUtil.filterCallableOperations does.

[Matthias Schoettle]

Might be suitable as a "getting into the project issue" (once sufficient knowledge has been acquired).

[Matthias Schoettle]

Another problem is, that it contains AssociationEnds that are non-navigable. These need to be filtered out as well.