Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Make runtime exceptions explainable #1456
Currently there are several places when Umple at runtime raises an exception due to various situations occurring.
For example the following code is found in https://cruise.eecs.uottawa.ca/umple/AssociationDefinition.html
An A can only have one associated B, so in the constructor of A there is code that may fail the construction due to the presence of the B. The generated code thus throws an exception as follows:
The trouble is, when code is executing, and this message appears in a stack trace, the end-user will not have a clue what is going on. Even the beginner Umple developer may not understand, since they are not generally supposed to be looking at the generated code.
What is needed is:
To find the places where runtime exceptions are thrown in Java go to umple/UmpleToJava/UmpleTLTemplates and do
The result lists 8 places, including