[Uml-devel] [Bug 72042] code generation ignores unidirectional association

[Oliver Kellogg]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=72042         




------- Additional Comments From okellogg users sourceforge net  2007-02-24 08:17 -------
> The patch try to create nothing when there is already a attribute
> with the same name that the role name

That's a very good idea and I think we need that for the other
association types too (aggregations, compositions)

>  (the role name to consider is the role A name).

Here is a UniAssociation in Umbrello (I hope whitespace is preserved):

+--------+         roleB +--------+
| Class1 |-------------->| Class2 |
+--------+               +--------+

The role A is at Class1 and the role B is at Class2.
Now the UML standard says the member name in Class1 should be
the role B name. So it's the role name "farther away" from the
referencing class - in the case of UniAssociation, the name
at the arrow head.

> But, in trunk, I wasn't able to add an attribute ?

Trunk still needs a lot of work.