directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r969774 - in /websites/staging/directory/trunk/content: ./ api/user-guide/4.2.1-schema-objects.html api/user-guide/6.12-entry.html
Date Wed, 21 Oct 2015 16:00:35 GMT
Author: buildbot
Date: Wed Oct 21 16:00:34 2015
New Revision: 969774

Staging update by buildbot for directory

    websites/staging/directory/trunk/content/   (props changed)

Propchange: websites/staging/directory/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Wed Oct 21 16:00:34 2015
@@ -1 +1 @@

Modified: websites/staging/directory/trunk/content/api/user-guide/4.2.1-schema-objects.html
--- websites/staging/directory/trunk/content/api/user-guide/4.2.1-schema-objects.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/4.2.1-schema-objects.html Wed
Oct 21 16:00:34 2015
@@ -258,10 +258,10 @@ h2:hover > .headerlink, h3:hover > .head
 <p>The last three elements are ApacheDS specific.</p>
 <p>All those elements have some tight relationships. The following schema expose all
the relations between all those elements :</p>
-<p><img alt="" src="../../images/SchemaObjects.png" /></p>
+<p><img alt="" src="images/SchemaObjects.png" /></p>
 <h2 id="java-class-hierarchy">Java Class hierarchy<a class="headerlink" href="#java-class-hierarchy"
title="Permanent link">&para;</a></h2>
 <p>Here is the relation between the various Java classes that are implementing the
various <strong>SchemaObject</strong>s elements :</p>
-<p><img alt="" src="../../images/schemaObjectHier.png" /></p>
+<p><img alt="" src="images/SchemaObjectHier.png" /></p>
 <p>As we can see, the 3 specific <strong>SchemaObject</strong>s are derived
from a <strong>LoadableSchemaObject</strong> abstract class, which allows the
developper to inject a new instance of one of those 3 <strong>SchemaObject</strong>s.</p>
 <p>From teh developper point of view, the interesting methods are the following :</p>

Modified: websites/staging/directory/trunk/content/api/user-guide/6.12-entry.html
--- websites/staging/directory/trunk/content/api/user-guide/6.12-entry.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/6.12-entry.html Wed Oct 21 16:00:34
@@ -190,7 +190,7 @@ h2:hover > .headerlink, h3:hover > .head
 <p>We also provide a few extended classes, like the <em>ImmutableEntry</em>,
an immutable version of the <em>Entry</em>.</p>
 <h2 id="what-is-an-entry">What is an entry ?<a class="headerlink" href="#what-is-an-entry"
title="Permanent link">&para;</a></h2>
 <p>An entry is an object containing a <em>Dn</em> and some <em>Attributes</em>.
The following schema shows what's inside an <em>entry</em> :</p>
-<p><img alt="" src="../../images/entry.png" /></p>
+<p><img alt="" src="images/entry.png" /></p>
 <h2 id="creating-an-entry">Creating an Entry<a class="headerlink" href="#creating-an-entry"
title="Permanent link">&para;</a></h2>
 <p>We have many ways to create an <em>Entry</em>. Basically, an <em>Entry</em>
has a <em>Dn</em> and some <em>Attributes</em>. It can be schema aware,
or not. We provide constructors to allow a user to create the kind of <em>Entry</em>
he wants.</p>
 <p>The simplest way to create an <em>Entry</em> is to call the default
constructor. The created entry will have no attributes, and no <em>Dn</em>. We
can also make it schema aware by passing a <em>SchemaManager</em>. Here is an

View raw message