directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r1034524 - in /websites/staging/directory/trunk/content: ./ api/user-guide/4.1-schema.html api/user-guide/4.2-schema-manager.html
Date Thu, 30 Aug 2018 07:46:40 GMT
Author: buildbot
Date: Thu Aug 30 07:46:40 2018
New Revision: 1034524

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/api/user-guide/4.1-schema.html
    websites/staging/directory/trunk/content/api/user-guide/4.2-schema-manager.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Aug 30 07:46:40 2018
@@ -1 +1 @@
-1839634
+1839642

Modified: websites/staging/directory/trunk/content/api/user-guide/4.1-schema.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide/4.1-schema.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/4.1-schema.html Thu Aug 30 07:46:40
2018
@@ -189,8 +189,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="41-schema">4.1 - Schema<a class="headerlink" href="#41-schema" title="Permanent
link">&para;</a></h1>
-<p>A <strong>Schema</strong> is a set of elements that are used by the
<strong>LDAP Server</strong> to describe the data that are stored. The top two
elements are <strong>ObjectClass* and </strong>AttributeType<strong>. An
</strong>ObjectClass<strong> is a container, describing what an </strong>LDAP<strong>
entry can contain, while an </strong>AttributeType** describe each singe element stored
in this container.</p>
-<p>The key here is that an <strong>LDAP</strong> entry uses <strong>ObjectClasses</strong>
to list all the possible <strong>AttributeTypes</strong> that entry can contain,
some of them being mandatory, some other optional.</p>
+<p>A <strong>Schema</strong> is a set of elements that are used by the
<strong>LDAP Server</strong> to describe the data that are stored. The top two
elements are <strong>ObjectClass</strong> and <strong>AttributeType</strong>.
An <strong>ObjectClass</strong> is a container, describing what an <strong>LDAP</strong>
entry can contain, while an <strong>AttributeType</strong> describe each singe
element stored in this container.</p>
+<p>The key here is that an <strong>LDAP</strong> entry uses <strong>ObjectClasses</strong>
to list all the possible <strong>AttributeTypes</strong> that an entry can contain,
some of them being mandatory, some other optional.</p>
 <p>Now, there is more. We have many other <strong>Schema Objects</strong>
that are colateral:</p>
 <ul>
 <li><strong>LdapComparator</strong> (<em>ApacheDS</em> specific)</li>

Modified: websites/staging/directory/trunk/content/api/user-guide/4.2-schema-manager.html
==============================================================================
--- websites/staging/directory/trunk/content/api/user-guide/4.2-schema-manager.html (original)
+++ websites/staging/directory/trunk/content/api/user-guide/4.2-schema-manager.html Thu Aug
30 07:46:40 2018
@@ -189,7 +189,7 @@
 }
 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="42-schema-manager">4.2 - Schema Manager<a class="headerlink" href="#42-schema-manager"
title="Permanent link">&para;</a></h1>
-<p>The API and the ApacheDS server components must to keep schema elements available
to interroate and use. This is done through what we call a <strong>SchemaManager</strong>.
It hides the internal structure of the schema objects from the users.</p>
+<p>The API and the ApacheDS server components must to keep schema elements available
to interrogate and use. This is done through what we call a <strong>SchemaManager</strong>.
It hides the internal structure of the schema objects from the users.</p>
 <h2 id="contents">Contents<a class="headerlink" href="#contents" title="Permanent
link">&para;</a></h2>
 <ul>
 <li><a href="4.2.1-schema-objects.html">SchemaObjects</a><ul>
@@ -209,7 +209,9 @@ h2:hover > .headerlink, h3:hover > .head
 </ul>
 <h2 id="introduction">Introduction<a class="headerlink" href="#introduction" title="Permanent
link">&para;</a></h2>
 <p>The <strong>SchemaManager</strong> stores all the Schema elements (<strong><a
href="">AttributeTypes (e)</a></strong>, <strong><a href="">ObjectClasses
(e)</a></strong>, ... Internally, we store these elements into what is call a
<strong>Registries</strong>.  Registries are hives where each Schema Object is
stored. Each schema element has a dedicated <strong>Registry</strong> associated
with it. Think of it as a Map which returns a reference to a specific Schema Element according
to its name or OID.</p>
-<div class="codehilite"><pre><span class="n">Note</span> <span
class="o">:</span> <span class="k">each</span> <span class="n">Schema</span>
<span class="n">Element</span> <span class="k">is</span> <span
class="n">properly</span> <span class="n">defined</span> <span class="n">by</span>
<span class="n">one</span> <span class="n">of</span> <span class="n">its</span>
<span class="n">names</span> <span class="n">or</span> <span class="n">OID</span><span
class="o">.</span> <span class="n">The</span> <span class="n">OID</span>
<span class="n">must</span> <span class="n">be</span> <span class="n">unique</span>
<span class="n">across</span> <span class="n">all</span> <span
class="n">schema</span> <span class="n">elements</span><span class="o">,</span>
<span class="n">when</span> <span class="n">the</span> <span class="n">name</span>
<span class="n">can</span> <span class="n">be</span> <span class="n">used</span>
<span class="k">in</span> <span class="n">different</span> <span
class="n">schem
 a</span> <span class="n">element</span> <span class="o">(</span><span
class="k">for</span> <span class="n">instance</span><span class="o">,</span>
<span class="n">the</span> <span class="o">**</span><span class="n">audio</span><span
class="o">**</span> <span class="n">AttributeType</span> <span class="n">or</span>
<span class="n">ObjectClass</span><span class="o">)</span>
+<div class="codehilite"><pre><span class="n">Note</span> <span
class="o">:</span> 
+<span class="k">each</span> <span class="n">Schema</span> <span
class="n">Element</span> <span class="k">is</span> <span class="n">properly</span>
<span class="n">defined</span> <span class="n">by</span> <span
class="n">one</span> <span class="n">of</span> <span class="n">its</span>
<span class="n">names</span> <span class="n">or</span> <span class="n">OID</span><span
class="o">.</span> <span class="n">The</span> <span class="n">OID</span>
<span class="n">must</span> <span class="n">be</span> <span class="n">unique</span>
<span class="n">across</span> <span class="n">all</span> <span
class="n">schema</span> <span class="n">elements</span><span class="o">,</span>

+<span class="n">when</span> <span class="n">the</span> <span class="n">name</span>
<span class="n">can</span> <span class="n">be</span> <span class="n">used</span>
<span class="k">in</span> <span class="n">different</span> <span
class="n">schema</span> <span class="n">element</span> <span class="o">(</span><span
class="k">for</span> <span class="n">instance</span><span class="o">,</span>
<span class="n">the</span> <span class="o">**</span><span class="n">audio</span><span
class="o">**</span> <span class="n">AttributeType</span> <span class="n">or</span>
<span class="n">ObjectClass</span><span class="o">)</span>
 </pre></div>
 
 



Mime
View raw message