openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r518192 - in /incubator/openjpa/trunk/openjpa-project/src/doc/manual: jpa_overview_meta.xml ref_guide_meta.xml
Date Wed, 14 Mar 2007 15:46:44 GMT
Author: kwsutter
Date: Wed Mar 14 08:46:43 2007
New Revision: 518192

Slight updates to the manual to connect the JPA CascadeType.REMOVE processing with the OpenJPA
@dependent annotation.

This is in response to the dev mailing list discussion:


Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_meta.xml
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_meta.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/jpa_overview_meta.xml Wed Mar 14
08:46:43 2007
@@ -1324,6 +1324,13 @@
+                <note>
+                	<para>
+OpenJPA offers enhancements to JPA's CascadeType.REMOVE functionality,
+including additional annotations to control how and when dependent fields will
+be removed.  See <xref linkend="dependent"/> for more details.
+                	</para>
+                </note>
 <classname>CascadeType</classname> defines one additional value, <literal>
 CascadeType.ALL</literal>, that acts as a shortcut for all of the values above.

Modified: incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml
--- incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml (original)
+++ incubator/openjpa/trunk/openjpa-project/src/doc/manual/ref_guide_meta.xml Wed Mar 14 08:46:43
@@ -569,9 +569,11 @@
 <literal>Magazine.coverArticle</literal> to a new <classname>Article</classname>
 instance will automatically delete the old <classname>Article</classname> stored
 in the field. Similarly, deleting a <classname>Magazine</classname> object will
-automatically delete its current cover <classname>Article</classname>. You can
-prevent an orphaned dependent object from being deleted by assigning it to
-another relation in the same transaction.
+automatically delete its current cover <classname>Article</classname>. (This
+latter processing is analogous to using JPA's CascadeType.REMOVE functionality
+as described in <xref linkend="jpa_overview_meta_cascade"/>.) You can
+prevent an orphaned dependent object from being automatically deleted by 
+assigning it to another relation in the same transaction.
 OpenJPA offers a family of marker annotations to denote dependent relations in

View raw message