[ http://jira.andromda.org/browse/EJB-53?page=comments#action_15090 ]
Vance Karimi commented on EJB-53: --------------------------------- After many days of debugging, I could not work out a way to avoid having to model the Entity stereotype as well as the MappedSuperclass stereotype and have a working uml2 model. I will be applying a patch to roll back this part of the original patch in the next day or two. This will mean that to model a mapped superclass, you will need to model the Entity and MappedSuperclass stereotypes on the class, as was the case originally with the cartridge. If there are any objections, feel free to have a stab at this. > Wrong class reference of associations of a MappedSuperclass > ----------------------------------------------------------- > > Key: EJB-53 > URL: http://jira.andromda.org/browse/EJB-53 > Project: EJB Cartridge > Type: Bug > Reporter: Karl-Heinz Walk > Assignee: Vance Karimi > Priority: Critical > > A modelled entity "XXX" with stereotype <<MappedSuperclass>> which has an > association to an entity "YYY" is named "XXXEmbeddable". But in the class > "YYY" the association definition is of class "XXX" instead of > "XXXEmbeddable". The generated code can't be compiled. > To solve this bug I suggest that explicitly modelled mapped superclasses are > NOT renamed to "XXXEmbeddable" but simply named "XXX". -- 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: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
