Link(s) between Object(s) in CollaborationDiagram(s) cause problems when
running AndroMDA
-----------------------------------------------------------------------------------------
Key: UMLMETA-50
URL: http://jira.andromda.org/browse/UMLMETA-50
Project: UML Metafacades
Type: Bug
Versions: 3.1RC1
Environment: Magicdraw 9.5 model, Linux 2.6 kernel, maven 1.0.2
Reporter: Brian Purvis
Assigned to: Wouter Zoons
Priority: Minor
Link(s) between Object(s) in CollaborationDiagram(s) cause problems when
running androMDA. Apparently the proper behavior would be for AndroMDA to
ignore these since they are NOT in ClassDiagram(s). Apparently AndroMDA thinks
these are Association(s) that it should be processing and complains because
there is no "type" on one end of the Association.
i.e.
INFO [AndroMDA] - validating model -
ERROR [AndroMDA] Model Validation Failed - 1 VALIDATION ERROR
ERROR [AndroMDA] 1) [undefined]:Each association end needs a type, you cannot
leave the type unspecified.
org.andromda.core.ModelValidationException: Model validation failed!
Association(s) in ImplementationDiagram(s) do NOT cause this bug.
I have NOT tried recreating this bug in the other types of diagrams but it
seems logical they could cause problems also.
The workaround is simply to keep these kinds of diagrams out of the model
processed by AndroMDA. Nonetheless, the ability to keep multiple types of
diagrams in the same model and still process the model with AndroMDA is a plus.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
