ignored <<Identifier>> association ends
---------------------------------------
Key: EJB-72
URL: http://jira.andromda.org/browse/EJB-72
Project: EJB Cartridge
Type: Bug
Reporter: Luca Dall'Olio
Assigned to: Vance Karimi
<<Identifier>> stereotypes on association ends are ignored during code
generation.
This usage of <<Identifier>> would be useful when mapping a cascade of
composite PKs, an example following :
Table schema :
TB_GRANDFATHER
PK : GRANDFATHER_NAME (VARCHAR)
TB_FATHER
PK,FK : GRANDFATHER_NAME (VARCHAR)
PK : FATHER_NAME (VARCHAR)
TB_CHILD
PK,FK : GRANDFATHER_NAME (VARCHAR)
PK,FK : FATHER_NAME (VARCHAR)
PK : CHILD_NAME (VARCHAR)
Domain Objects :
<<Entity>> <<Entity>>
<<Entity>>
GrandFather 1 <<Ident.>> ---- 1..* Father 1
<<Ident.>> ----- 1..* Child
<<Ident.>> gname :: String <<Ident.>> fname :: String
<<Ident.>> cname :: String
--
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: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
