Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 1.2.0
-
Fix Version/s: x.x
-
Component/s: DSL for Business Domain
-
Labels:None
-
Number of attachments :
Description
The role name of the many end of a one-to-many association cannot be the (case-insensitively) same as the name of the class at the many end. This is because code is generated to iterate through the elements of the Set corresponding to the association that uses the but with a lowercase first letter as the name of variable for the element in each loop iteration. That name conflicts with the name of the association that is also derived from the classname with a lowercase first letter.
Activity
Eric Jan Malotaux
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Eric Jan Malotaux [ eric.malotaux ] |
Eric Jan Malotaux
made changes -
| Fix Version/s | 1.3.0 [ 16187 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
Jos Warmer
made changes -
| Status | Resolved [ 5 ] | Closed [ 6 ] |
Eric Jan Malotaux
made changes -
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Resolution | Fixed [ 1 ] |
Eric Jan Malotaux
made changes -
| Status | Reopened [ 4 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
Johan Vogelzang
made changes -
| Fix Version/s | 2.0 [ 16488 ] | |
| Fix Version/s | 1.3.0 [ 16187 ] |
A simple work-around is to always use for the role name the plural form of the noun used as class name. That way they are (almost) always different.