[ http://jira.andromda.org/browse/EJB-53?page=comments#action_15100 ]
Vance Karimi commented on EJB-53: --------------------------------- I've applied this patch. You now need to model the Entity and MappedSuperclass stereotypes again, but you should not longer have the problem with uml2 models. Can one of the guys watching this issue pls try this fix and provide feedback. > 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 ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
