From: Vance K. <va...@us...> - 2006-02-09 07:15:27
|
User: vancek Date: 06/02/08 23:15:21 Modified: andromda-ejb3/src/main/resources/META-INF/andromda profile.xml Log: added COLUMN_INSERT and COLUMN_UPDATE elements defining corresponding tagged values for mapped properties Revision Changes Path 1.15 +30 -0 cartridges/andromda-ejb3/src/main/resources/META-INF/andromda/profile.xml Index: profile.xml =================================================================== RCS file: /cvsroot/andromdaplugins/cartridges/andromda-ejb3/src/main/resources/META-INF/andromda/profile.xml,v retrieving revision 1.14 retrieving revision 1.15 diff -u -w -r1.14 -r1.15 --- profile.xml 8 Feb 2006 10:12:52 -0000 1.14 +++ profile.xml 9 Feb 2006 07:15:21 -0000 1.15 @@ -628,6 +628,36 @@ <value>false</value> </allowedValues> </element> + <element name="COLUMN_INSERT"> + <documentation> + Specifies whether a mapped column should be included + in SQL INSERT statements. Setting to <code>false</code> + allows the column to be initialized using other mechanisms + such as a value defaulted by thedatabase. Defaults to + <code>true</code>. + </documentation> + <value>@andromda.persistence.column.insert</value> + <appliedOnElement><![CDATA[<<Entity>>]]> Attribute</appliedOnElement> + <allowedValues> + <value default="true">true</value> + <value>false</value> + </allowedValues> + </element> + <element name="COLUMN_UPDATE"> + <documentation> + Specifies whether a mapped column should be included + in SQL UPDATE statements. Setting to <code>false</code> + allows the column to be updated using other mechanisms + such as a value defaulted by the database. Defaults to + <code>true</code>. + </documentation> + <value>@andromda.persistence.column.update</value> + <appliedOnElement><![CDATA[<<Entity>>]]> Attribute</appliedOnElement> + <allowedValues> + <value default="true">true</value> + <value>false</value> + </allowedValues> + </element> <element name="ORDER_BY"> <documentation> Specifies the column name(s) that will be |