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

Antoine Dopffer adopffer at nerdshack.com
Sat Feb 24 09:05:40 UTC 2007

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

------- Additional Comments From adopffer nerdshack com  2007-02-24 10:05 -------
sorry for I took the wrong way of the arrow.
I think I am kind of UML dyslexiac.

The check against attributes was created because I was affraid that attributes could be generated twice in this situation:

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

roleB (declaration, getter, setter) could be generated because roleB is the role B name of the unidirectional association

roleB (declaration, getter, setter) could be also generated once again because roleB is an attribute of Class1

To get this kind of diagram with Umbrello, you have to delete the agregation that is automatically generated when you add attribute roleB in C1

More information about the umbrello-devel mailing list