Array not added to structural view on import

[Matthias Schoettle]

When an operation for an implementation class is imported, which has an array as a parameter type, it is created on the fly. However, it is never added to the structural view's types, which results in problems when saving (dangling href).

[Matthias Schoettle]

Resolves #300: Adds the adding of arrays to the structural view when one is created on the fly.

→ <<cset 458aea5c9233>>

[Matthias Schoettle]

References #300: Fixes an issue, where an array is added multiple times, even if it exists already. Instead, the creation of the array is delegated to the existing getTypeByName method of RamModelUtils.

→ <<cset 11c2c58b41f3>>

[Matthias Schoettle]

By fixing this issue, a new one was introduced, which occurs if a type cannot be found and it is an array. This is the case with byte[], because byte is currently not defined in the metamodel as a primitive type. See #443.

Instead of continuing, the getType method should just return null, because this return is only used to compare with existing methods. This would just mean that an already imported method will be shown in the selector again.

[Matthias Schoettle]

Resolves #300 again: Only process arrays if a type was found.

→ <<cset 6e92cb30ee86>>