Incomplete code generated from association used as key #184
Assignees
Labels
associations
Related to umple associations
Component-SemanticsAndGen
Related to code generators in general and the meaning of Umple models
Diffic-Med
A non-trivial problem that may take over a week or may not be obvious how to fix or require analysis
Priority-High
This problem or enhancement is likely to be highly visible and or impactful of users
Status-Verified
Type-Defect
Comments
|
This problem exists whenever an association name is used as a key Just add ' key { Booking, SpecifcFlight}' to the Booking class in the airline example Reported by @umple on 2012-03-05 15:00:10 |
|
Reported by @umple on 2012-06-14 15:02:30
|
Nava2
added
Type-Defect
associations
|
Reported by @umple on 2012-09-27 19:44:52
|
|
I'll start looking into this Reported by
|
|
The problem had to do with Associations in key statements being expected to have a lower-case Reported by |
|
Reported by @umple on 2013-12-05 15:06:27
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally reported on Google Code with ID 284
Owned by
fkazhamiakaWhat steps will reproduce the problem?
Type the following code
class A
{
1 -- 1 B;
key {B};
}
class B
{
Integer id;
key {id};
}
What is the expected output? What do you see instead?
public boolean equals(Object obj)
{
if (obj == null) { return false; }
if (!getClass().equals(obj.getClass())) { return false; }
A compareTo = (A)obj;
return true;
}
See also issue 226 for another 1-1 problem
Reported by @umple on 2012-03-05 14:43:26
The text was updated successfully, but these errors were encountered: