OCL not initialized when creating a new aspect

[Matthias Schoettle]

After the recent changes (issue #83) OCL is not loaded anymore in all cases. When starting TouchRAM and creating a new aspect, the following exception will occur when creating a new operation:

Exception in thread "Animation Thread" java.lang.UnsupportedOperationException: eInvoke not implemented for getName
    at org.eclipse.emf.ecore.util.BasicInvocationDelegate.dynamicInvoke(BasicInvocationDelegate.java:90)
    at ca.mcgill.cs.sel.ram.impl.RBooleanImpl.getName(RBooleanImpl.java:65)
    at ca.mcgill.ram.utils.RamModelUtils.getType(RamModelUtils.java:400)
    at ca.mcgill.ram.utils.RamModelUtils.getType(RamModelUtils.java:340)

[Matthias Schoettle]

Resolved issue #84: ResourceManager needs to be loaded explicitly. Otherwise, OCL won't be initialized when the user creates a new aspect directly after loading TouchRAM.

Furthermore, the ResourceManager will only initialize everything once. Subsequent calls don't have any effect.

→ <<cset 88a80feadb67>>

[Matthias Schoettle]

References issue #84: Added the option to explicitly initialize the ResourceManager without OCL.

→ <<cset 2e1a8a5029c3>>