Umple Code generation bug

[Thomas Kuehne]

Hi,

the following seems unsuitable for stackoverflow, hence I'm posting here.

It seems very recently a problem with Java code generation was introduced. I'm positive that this bug didn't exist about 24h hours ago because I saved my Umple files which were working back then.

I reported the issue as issue #1341 ("Incorrect Exception Handling Java Code Generation") to the Umple issue tracker. Please let me know if I should repeat it here.

BTW, I'm including a "public static void main(...)" method in order to be able to quickly run the code generated by Umple. Please let me know if I should do that differently.

Would you advise against using Umple online in university labs? It seems dangerous to use Umple online for assessed labs when code generation can break like that. I currently have a workaround but would it be conceivable that my students would be faced with a dynamically introduced bug for which I wouldn't be able to think of a workaround or simply not be around to help them (we have too many lab sessions for me to attend them all).

Cheers,

  Thomas

[Timothy Lethbridge]

Hi,

I have been unable to reproduce this issue. Please would you look at the issue comment at

https://github.com/umple/umple/issues/1341

and follow up with further discussion there. There may be a legitimate bug, but when I enter a complete model with the main method you provided, it does not occur.

As for using UmpleOnline in university labs, a very large number of people do indeed do so, and we have not encountered many showstopper bugs. We will stamp this one out once we can reproduce it.

I don't believe this bug was introduced in the last 24h, but I stand to be corrected. 

For university labs, we recommend students use UmpleOnline on their local machines via Docker. See http://docker.umple.org

There is a udock script in the umple dev-tools folder that can facilitate use of docker for users of Linux and Macintosh

Docker guarantees them a stable environment.

But stability is generally guaranteed anyway. We run each version of Umple through many thousands of tests, and code is not allowed to change from version to version except as precisely expected. We also compile all generated code.

Finally stability is guaranteed in another way: During 'academic term' many few pull requests go through. This summer we are much more busy.

But your thoughts about stability will be taken into account, and maybe we should adapt UmpleOnline with a flag that by default uses only the latest official release, but can be switched to use the latest update if the user desires.

[Thomas Kuehne]

Hi,

I've made a source file + the incorrect code that is generated from it available to you (via private email). I hope you can reproduce the problem with this data. As I explained in the email, I'd prefer the code not to become available publicly (it isn't much at all, but still, I'd love to use the code as the basis for a bigger example).

Please accept my apologies if I came across as being overly concerned with Umple's stability. Indeed, at first it seemed that the only factor that could have changed would be an updated code generator. However, it may be another (potentially difficult to identify) factor that causes the code generation issue to occur. If you cannot reproduce the problem, I'll promise to investigate myself, once I got my example fully developed.

I have full confidence that UmpleOnline will work and have not spend a second on discarding the idea of using UmpleOnline. Your recommendation to use Docker is of course spot on. It would help with performance as well. I just haven't had a chance yet to look into using Docker but I know where the respective Umple documentation is. I'll also look at the option of using an Eclipse plugin.

[Timothy Lethbridge]

OK. Upon receipt of your confidential code, we have reproduced, and will work to create an urgent fix