Frequently Asked Questions (FAQ)

Q: Running or debugging a model gives validation errors, but they are not shown in the editor.
A: If the editor reports no validation errors, but running or debugging the model reports errors, then there might be a problem with the line endings of the files. To solve this problem, save the file with windows line endings. This problem is often caused by Linux line endings.

Q: Why does the type system produce warnings instead of errors?
A: In POOSL models, the types of variables and parameters have no formal meaning; basically they are just pieces of documentation. When invoking a data method or operation, at simulation time the types of variables are determined. This means that it is impossible to perform a 100% correct type check while editing; therefore any data type related issues are reported while editing as warnings.

Q: Why does a certain quick-fix have no effect?
A: Executing a quick-fix sometimes has no effect on the model. This can be caused by other errors that are still present in the model that are related to applied quick-fix. Solve these errors before executing the quick-fix.

Q: Why does "Help -> Check for Updates" not show any updates for Rotalumis?
A: Updates for the POOSL IDE and Rotalumis plugins are released independently. To make sure that you are notified of Rotalumis updates, check that Rotalumis occurs in Help -> About Eclipse -> Installation Details -> Installed Software. If Rotalumis does not occur, please explicitly install Rotalumis (from the POOSL IDE update site); see the installation manual.

Q: What can I do about "OutOfMemoryError: Java heap space" or "GC overhead limit exceeded"?
A: The Eclipse installation folder contains a file eclipse.ini, which most likely contains a fragment like "-Xmx512m". This indicates that the maximum Java heap size is 512 megabyte. Increasing this amount (e.g., doubling it) should solve this problem.

Q: What can I do about the error "Zero representations file found in "...". A modeling project must contain one."?
A: This means that the project has a modeling nature but does not contain an .aird file. The Modeling nature and .aird file are needed for graphical editing and are automatically added when opening a graphical editor.
There are 2 ways to fix this error:

  1. Remove the representations.aird:
    See the next question What is the file representations.aird, and how can I remove it?.
  2. Open a graphical editor:
    It doesn't matter which diagram you open, the representations.aird file will automatically be generated. To open a class diagram right click a .poosl file and select "Open Class Diagram".

Q: What is the file representations.aird, and how can I remove it?
A: The .aird file stores the graphical model information, and is automatically added when opening a graphical editor. To remove this file, first remove the Modeling nature from the project by right clicking the project in the Project Explorer -> Configure -> Remove Modeling Project Nature. If "Remove Modeling Project Nature" is not present, then the Modeling nature has already been removed. Once the Modeling nature is removed, you can safely remove the representations.aird file: right click the representation.aird and select delete.