Converting UML to java is really very bad. Besides Omondo, using either synchronous synchronization of a diagram, or a diagram, or synchronous synchronization of a model, and then merging the UML and Java identifiers to deliver high-quality code, all the other tools are just crap! I mean that:
- Why generate code using only one package?
- why mix class and interfaces in one package. It is so stupid for a java architect to mix a class and its associated interface, so why does UML consider both to be in the same package for code generation purposes? why inheritance is not created if it does not work in one package? How dare you say that UML is object modeling if you mix something that should not be mixed in order to have dirty code generation?
This Model Driven development is so mediocre that I stopped using it, and only live coding and model synchronization provide an acceptable solution. I model and get my code, if my code is not the one that I think is good, then I change my code and my diagram is updated. I can add java annotation to my code and my diagrams, so my model can be immediately deployed and tested, it won't be a more painful stupid test, etc ...
UML may be fantastic, but model-based development was full of incredible lies! Unproductive modelers who have never executed any manual line of java code are trying to create architectures and code and provide them to us (for example, a developer) to complete the work. Printed documentation is not suitable, etc.
There is no code generation, because if you use Omondo EclipseUML, you will understand how the code should be generated. This is UML with live code and model synchronization. I got my model and then completely reorganize my code manually without losing the model and diagrams. Great technology if used with Hibernate, because my charts can be deployed in real time and tested using java annotations. Whaoo
UML GURU
source share