| Summary: | AssociationEnds don't include role name or comment | ||
|---|---|---|---|
| Product: | [Applications] umbrello | Reporter: | Jörg Walter <trouble> |
| Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | assoc.xmi - produced using KDE SVN branches/3.5/KDE/kdesdk/umbrello | ||
|
Description
Jörg Walter
2006-03-15 09:27:37 UTC
The problem has to do with the way Umbrello automatically maps class attributes to associations, see UMLView::createAutoAttributeAssociations(). The AssociationWidget is not bound to an UMLAssociation but to an UMLAttribute. I.e. the association is merely rendered in the diagram but does not exist as a model object. No, I'm not talking about automatic associations created by properties, but classic hand-made connections. These show up as <UML:Association> elements with two <UML:AssociationEnd> tags, but the "name" attribute on these <UML:AssociationEnd> tags is always empty, and the comment is missing, although the GUI has separate input fields for tag comments. In the case of the "name" attribute, I am able to extract the text from the assocwidget, which is annoying but a decent workaround. In the case of the comment, it doesn't appear anywhere in the XMI file. Created attachment 15168 [details]
assoc.xmi - produced using KDE SVN branches/3.5/KDE/kdesdk/umbrello
Thanks for clarifying - I cannot reproduce your observation.
The attached XMI file has an association like this:
+------------+ +-----------+
| | multiA multiB | |
| nova_klaso |<>----------------------------------| new_class |
| | roleAName assocName roleBName | |
+------------+ +-----------+
Name, rolenames, multiplicities, and documentations were entered
in the Properties dialog and appear in the XMI file as expected.
Yes, you are right. It works in KDE 3.5.1. I wasn't aware that there was a new release, sorry for the trouble. *** Bug has been marked as fixed ***. |