cayenne-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From aadamc...@apache.org
Subject svn commit: r1586847 - /cayenne/main/trunk/docs/docbook/cayenne-guide/src/docbkx/lifecycle-events.xml
Date Sat, 12 Apr 2014 10:51:52 GMT
Author: aadamchik
Date: Sat Apr 12 10:51:51 2014
New Revision: 1586847

URL: http://svn.apache.org/r1586847
Log:
fixing the docs to refelect the new reality with callbacks

Modified:
    cayenne/main/trunk/docs/docbook/cayenne-guide/src/docbkx/lifecycle-events.xml

Modified: cayenne/main/trunk/docs/docbook/cayenne-guide/src/docbkx/lifecycle-events.xml
URL: http://svn.apache.org/viewvc/cayenne/main/trunk/docs/docbook/cayenne-guide/src/docbkx/lifecycle-events.xml?rev=1586847&r1=1586846&r2=1586847&view=diff
==============================================================================
--- cayenne/main/trunk/docs/docbook/cayenne-guide/src/docbkx/lifecycle-events.xml (original)
+++ cayenne/main/trunk/docs/docbook/cayenne-guide/src/docbkx/lifecycle-events.xml Sat Apr
12 10:51:51 2014
@@ -151,20 +151,6 @@ public class Order extends _Order {
     </section>
     <section xml:id="callback-non-persistent">
         <title>Callbacks on Non-Persistent Listeners</title>
-        
-            <para>
-                <note>
-                    <para>While listener callback methods can be declared in the Modeler
(at least
-                        as of this wrting), which ensures their automatic registration in
runtime,
-                        there's a big downside to it. The power of the listeners lies in
their
-                        complete separation from the XML mapping. The mapping once created,
can be
-                        reused in different contexts each having a different set of listeners.
-                        Placing a Java class of the listener in the XML mapping, and relying
on
-                        Cayenne to instantiate the listeners severly limits mapping reusability.
-                        Further down in this chapter we'll assume that the listener classes
are
-                        never present in the DataMap and are registered via API.</para>
-                </note>
-            </para>
             <para>A listener is simply some application class that has one or more
annotated
             callback methods. A callback method signature should be <code>void
                 someMethod(SomePersistentType object)</code>. It can be public, private,
protected



Mime
View raw message