Importing Together-6.0.1 UML-1.4 models and Java c

[sunset]

Thanks Simon.
Indeed after such mishaps we checked this option and others.

It is interesting to know that EA doesn't check the model that much. This confirms that it allows lots of diagrams to be wrong. For example, an interface having associations... and it generates such code! Is there a way to enforce basic OO checks?

[«Midnight»]

You can check a diagram or package for validity. See the EA main menu under Project | Model Validation, and look at the dialog. There are several related options regarding what to check and what to exclude. You can also write your own rules.

This is quite another matter when reverse engineering code (or reading external models). What EA reads in is the actual code (or model), valid or otherwise. So we're stuck with whatever structures are there need to be rendered. You can always validate and correct errors once you review the model in EA.

[sunset]

well, here is the simple test I did:
- check all options in model validation
- open a new class diagram
- add an interface and a class
- add an association between the two
- generate java code

Result: interface has attributes and class none... Clearly no check done and code completely wrong even not corresponding to the model.