Author: buildbot
Date: Thu Feb 21 11:55:38 2013
New Revision: 851400
Log:
Staging update by buildbot for cayenne
Modified:
websites/staging/cayenne/trunk/content/ (props changed)
websites/staging/cayenne/trunk/content/docs/3.1/cayenne-guide/lifecycle-events.html
Propchange: websites/staging/cayenne/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Feb 21 11:55:38 2013
@@ -1 +1 @@
-1448529
+1448614
Modified:
websites/staging/cayenne/trunk/content/docs/3.1/cayenne-guide/lifecycle-events.html
==============================================================================
---
websites/staging/cayenne/trunk/content/docs/3.1/cayenne-guide/lifecycle-events.html
(original)
+++
websites/staging/cayenne/trunk/content/docs/3.1/cayenne-guide/lifecycle-events.html
Thu Feb 21 11:55:38 2013
@@ -194,7 +194,7 @@ registry.addListener(<span xmlns="http:/
}</pre></div><div class="section" title="Combining Listeners with
DataChannelFilters"><div class="titlepage"><div><div><h2 class="title"><a
name="comining-listeners-with-datachannelfilters"></a>Combining Listeners with
DataChannelFilters</h2></div></div></div><p>A final touch in the listeners
design is preserving the state of the listener within a
single select or commit, so that events generated by multiple
objects can be collected
- and processed all together. To do that you will need to implements
a
+ and processed all together. To do that you will need to implement a
<code class="code">DataChannelFilter</code>, and add some
callback methods to it. They will store
their state in a ThreadLocal variable of the filter. Here is an
example filter that does
something pretty meaningless - counts how many total objects were
committed. However it