ManageableDaoBase creates wrong code with associations
------------------------------------------------------
Key: SPRING-158
URL: http://jira.andromda.org/browse/SPRING-158
Project: Spring Cartridge
Type: Bug
Components: CRUD
Versions: 3.2-RC1
Reporter: Andreas Spankus
Assigned to: Chad Brandon
by simply modelling 2 entities A and B and giving them the stereotypes
<<entity>> and <<manageable>>:
(A) 1 - * (B) with a composition at the A-end
the SpringCrudDaoBase.vsl generates wrong code around line 98:
...
#if ($member.otherEnd.navigable)
// set the other ends of the many2many association too
for (final java.util.Iterator iterator =
${memberEntityName}.iterator(); iterator.hasNext();)
{
final $member.type.fullyQualifiedName element =
($member.type.fullyQualifiedName)iterator.next();
element.${member.otherEnd.getterName}().add(entity);
}
#else
...
there is no many2many association, but code for that will be created.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
