directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r936618 - in /websites/staging/directory/trunk/content: ./ api/user-guide/2.6-modifying.html
Date Sun, 18 Jan 2015 11:18:19 GMT
Author: buildbot
Date: Sun Jan 18 11:18:19 2015
New Revision: 936618

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/api/user-guide/2.6-modifying.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Jan 18 11:18:19 2015
@@ -1 +1 @@
-1652736
+1652737

Modified: websites/staging/directory/trunk/content/api/user-guide/2.6-modifying.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide/2.6-modifying.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/2.6-modifying.html Sun Jan 18
11:18:19 2015
@@ -169,7 +169,7 @@
 
 <h1 id="26-modifying-entries">2.6 - Modifying entries</h1>
 <p>There are several ways an entry can be modified. Mainly, it's about adding or deleting
an attribute, or it's about modifying the values associated with an existing attribute.</p>
-<p>It's important to understand that many modifications can be applied on a single
entry. All those modifications will be applied in a all or none fashion. For instance, if
any one of the modifications is invalid, then none of the modifications will be applied. Also
if the server crashes while applying the modifications, it's guaranteed that the entry will
remain consistent.</p>
+<p>It's important to understand that many modifications can be applied on a single
entry. All those modifications will be applied in a all or none fashion. For instance, if
any of the modifications is invalid, then none of the modifications will be applied. Also
if the server crashes while applying the modifications, it's guaranteed that the entry will
remain consistent.</p>
 <h2 id="how-it-works">How it works ?</h2>
 <p>Each modification to be applied on an entry is encapsulated in an intermediate class
: a <em>Modification</em> instance, which can be created as :</p>
 <div class="codehilite"><pre><span class="n">Modification</span>
<span class="n">addedGivenName</span> <span class="o">=</span> <span
class="k">new</span> <span class="n">DefaultModification</span><span
class="o">(</span> <span class="n">ModificationOperation</span><span
class="o">.</span><span class="na">ADD_ATTRIBUTE</span><span class="o">,</span>
<span class="s">&quot;givenName&quot;</span><span class="o">,</span>
<span class="s">&quot;John&quot;</span><span class="o">,</span>
<span class="s">&quot;Peter&quot;</span> <span class="o">);</span>



Mime
View raw message