You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by bu...@apache.org on 2016/12/31 03:07:34 UTC
svn commit: r1003808 - in /websites/staging/directory/trunk/content: ./
api/user-guide.html api/user-guide/2.6-modifying.html
Author: buildbot
Date: Sat Dec 31 03:07:34 2016
New Revision: 1003808
Log:
Staging update by buildbot for directory
Modified:
websites/staging/directory/trunk/content/ (props changed)
websites/staging/directory/trunk/content/api/user-guide.html
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 Sat Dec 31 03:07:34 2016
@@ -1 +1 @@
-1776679
+1776680
Modified: websites/staging/directory/trunk/content/api/user-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide.html Sat Dec 31 03:07:34 2016
@@ -176,7 +176,7 @@ Other pages are finished (but may be rev
<h2 id="about-this-guide">About this guide<a class="headerlink" href="#about-this-guide" title="Permanent link">¶</a></h2>
<p>Getting started. Learn how to use the LDAP API, connect to various LDAP servers, manipulate the data within a directory. </p>
<h3 id="audience">Audience<a class="headerlink" href="#audience" title="Permanent link">¶</a></h3>
-<p>This guide is for anyone wanting to learn how to use the LDAP API. If you plan to use the API, maybe even for your first LDAP experience, you'll find information here to help. Right now we've got pretty good coverage of the basic tasks. Later, we'll add more advanced use cases so keep checking back. To learan about advanced options (and many other things) go to the [Advanced User's Guide].</p>
+<p>This guide is for anyone wanting to learn how to use the LDAP API. If you plan to use the API, maybe even for your first LDAP experience, you'll find information here to help. Right now we've got pretty good coverage of the basic tasks. Later, we'll add more advanced use cases so keep checking back. To learn about advanced options (and many other things) go to the [Advanced User's Guide].</p>
<h3 id="feedback-welcome">Feedback welcome!<a class="headerlink" href="#feedback-welcome" title="Permanent link">¶</a></h3>
<p>We are interested in improving the content of this guide. Feel free to provide feedback:
!email.png! <a href="mailto:users@directory.apache.org">mailto:users@directory.apache.org</a></p>
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 Sat Dec 31 03:07:34 2016
@@ -185,8 +185,8 @@
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
<h1 id="26-modifying-entries">2.6 - Modifying entries<a class="headerlink" href="#26-modifying-entries" title="Permanent link">¶</a></h1>
<p>There are several ways an entry can be modified. Mainly, it's about adding or deleting an attribute, or 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 an all or none fashion. i.e., if any of the modifications are invalid, none of them will occur. Also if the server crashes while applying the mods, it's guaranteed that the entry will remain consistent.</p>
-<h2 id="how-it-works">How it works ?<a class="headerlink" href="#how-it-works" title="Permanent link">¶</a></h2>
+<p>It's important to understand that many modifications can be applied on a single entry. All those modifications will be applied in an all or none fashion. i.e., if any of the modifications are invalid, none will occur. Also if the server crashes while applying the mods, it's guaranteed that the entry remains consistent.</p>
+<h2 id="how-it-works">How it works?<a class="headerlink" href="#how-it-works" title="Permanent link">¶</a></h2>
<p>Each modification to be applied on an entry is encapsulated into 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">"givenName"</span><span class="o">,</span> <span class="s">"John"</span><span class="o">,</span> <span class="s">"Peter"</span> <span class="o">);</span>
</pre></div>