Moving message calling an implementation class causes crash

[Matthias Schoettle]

Consider a message call to an operation of an implementation class. When attempting to move this message up/down, the following crash occurs:

Caused by: java.lang.IndexOutOfBoundsException: toIndex = 18
    at java.util.SubList.<init>(AbstractList.java:622)
    at java.util.RandomAccessSubList.<init>(AbstractList.java:775)
    at java.util.AbstractList.subList(AbstractList.java:484)
    at ca.mcgill.sel.ram.controller.FragmentsController.moveFragment(FragmentsController.java:850)
    at ca.mcgill.sel.ram.controller.MessageController.moveMessage(MessageController.java:239)
        ...

This is because there is no message view defined, which means nested message behaviour is considered to be present. A test case should cover this. However, since no nested message behaviour is possible anymore, this part could be removed completely.

[Matthias Schoettle]

References #504: Adds test case to capture moving of call to operation of implementation class.

→ <<cset 6869b0568173>>

[Matthias Schoettle]

Resolves #504: Removes handling of nested behaviour for implementation classes.

→ <<cset f53df768199f>>