From: Vance K. <va...@us...> - 2007-06-26 12:11:34
|
User: vancek Date: 07/06/26 05:11:36 Modified: andromda-ejb3/src/main/resources/META-INF/andromda namespace.xml Log: Expand entityInheritanceStrategy docs Revision Changes Path 1.41 +12 -4 cartridges/andromda-ejb3/src/main/resources/META-INF/andromda/namespace.xml Index: namespace.xml =================================================================== RCS file: /cvsroot/andromdaplugins/cartridges/andromda-ejb3/src/main/resources/META-INF/andromda/namespace.xml,v retrieving revision 1.40 retrieving revision 1.41 diff -u -w -r1.40 -r1.41 --- namespace.xml 14 Jun 2007 14:38:30 -0000 1.40 +++ namespace.xml 26 Jun 2007 12:11:35 -0000 1.41 @@ -816,12 +816,20 @@ </a> tagged value, can be the following possible values: <ul> - <li>SINGLE_TABLE - table per hierarchy.</li> <li> - TABLE_PER_CLASS - table per class in - hierarchy. + SINGLE_TABLE - A single table per class hierarchy. One table will have all + properties of every class in the hierarchy. + </li> + <li> + TABLE_PER_CLASS - A table per concrete class in the + hierarchy. Each class will have a table dedicated to it, with all of its + properties and the properties of its superclass mapped to this table. + </li> + <li> + JOINED - A table per subclass. Each class will have its own table. Each + table will have only the properties that are defined in that particular class. + These tables will not have properties of any superclass or subclass. </li> - <li>JOINED - Table per class.</li> </ul> </documentation> </property> |