Java constructor handling in UML -> Java reactions can lead to invalid Java code

[JanWittler]

Currently, we map operations in UML to constructors in Java if their name matches the name of the containing class, otherwise a Java class method is created. However, if later on such an UML method is renamed or made static, we do not check whether the corresponding java object is a constructor but perform the changes anyways. If the corresponding Java object was a constructor, this change will lead to an invalid state of the Java source file.

I know that this is just an edge case which will only occur rarely - if at all - but it should be documented anyways.