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 2013/06/17 01:18:09 UTC

svn commit: r865879 - in /websites/staging/directory/trunk/content: ./ apacheds/basic-ug/2.3.1-adding-schema-elements.html

Author: buildbot
Date: Sun Jun 16 23:18:09 2013
New Revision: 865879

Log:
Staging update by buildbot for directory

Modified:
    websites/staging/directory/trunk/content/   (props changed)
    websites/staging/directory/trunk/content/apacheds/basic-ug/2.3.1-adding-schema-elements.html

Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Jun 16 23:18:09 2013
@@ -1 +1 @@
-1493610
+1493611

Modified: websites/staging/directory/trunk/content/apacheds/basic-ug/2.3.1-adding-schema-elements.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/basic-ug/2.3.1-adding-schema-elements.html (original)
+++ websites/staging/directory/trunk/content/apacheds/basic-ug/2.3.1-adding-schema-elements.html Sun Jun 16 23:18:09 2013
@@ -183,8 +183,7 @@ It takes a few weeks to have a private O
 <h2 id="a-simple-example">A simple example</h2>
 <p>The goal is to store ship entries in our directory, backing the "Seven Seas" example used throughout the Basic User's Guide. There are no schema elements shipped with ApacheDS covering our naval requirements. So we add some.</p>
 <p>Here is a sample entry for a ship in LDIF:</p>
-<div class="codehilite"><pre>::: text
-dn: cn=HMS Victory,ou=ships,o=sevenSeas
+<div class="codehilite"><pre>dn: cn=HMS Victory,ou=ships,o=sevenSeas
 objectClass: top
 objectClass: ship
 cn: HMS Victory
@@ -197,8 +196,7 @@ description: built between 1759 and 1765
 <p>A ship entry is comprised of a mandatory value for common name (cn) of the ship, description values and the number of guns (numberOfGuns). Thus a new object class ship and a new attribute type numberOfGuns have to be added to the schema. There are different ways to accomplish the task. In any case, we have to add the attribute type first, because the object class refers to it.</p>
 <h4 id="attribute-type-numberofguns">attribute type numberOfGuns</h4>
 <p>Here is the definition of our custom attribute type numberOfGuns formatted according to RFC 4512.</p>
-<div class="codehilite"><pre>::: text
-( 1.3.6.1.4.1.18060.0.4.3.2.1 
+<div class="codehilite"><pre>( 1.3.6.1.4.1.18060.0.4.3.2.1 
  NAME &#39;numberOfGuns&#39;  DESC &#39;Number of guns of a ship&#39;
  EQUALITY integerMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 
  SINGLE-VALUE 
@@ -208,8 +206,7 @@ description: built between 1759 and 1765
 
 <h4 id="object-class-ship">object class ship</h4>
 <p>Custom object class ship is defined as follows</p>
-<div class="codehilite"><pre>::: text
-( 1.3.6.1.4.1.18060.0.4.3.3.1 
+<div class="codehilite"><pre>( 1.3.6.1.4.1.18060.0.4.3.3.1 
  NAME &#39;ship&#39; DESC &#39;An entry which represents a ship&#39; 
  SUP top STRUCTURAL 
  MUST cn MAY ( numberOfGuns $ description ) 
@@ -220,14 +217,14 @@ description: built between 1759 and 1765
 <h2 id="using-apache-directory-studio-schema-editor-to-load-the-new-schema-elements">Using Apache Directory Studio Schema Editor to load the new schema elements</h2>
 <p>A very convenient way to add your own schema elements to Apache Directory Server is to use the Schema Editor of Apache Directory Studio. It is even possible to define/design them within the UI, but we opt here use a prepared file in OpenLDAP format and import it using Studio. This is a good choice if you have the schema to add already described that way.</p>
 <p>Our file sevenSeas.schema looks like this:</p>
-<div class="codehilite"><pre>::: text
-attributetype ( 1.3.6.1.4.1.18060.0.4.3.2.1 
+<div class="codehilite"><pre>attributetype ( 1.3.6.1.4.1.18060.0.4.3.2.1 
         NAME &#39;numberOfGuns&#39; 
         DESC &#39;Number of guns of a ship&#39;
         EQUALITY integerMatch
         SYNTAX 1.3.6.1.4.1.1466.115.121.1.27 
         SINGLE-VALUE 
  )
+
 objectclass ( 1.3.6.1.4.1.18060.0.4.3.3.1 
         NAME &#39;ship&#39;
         DESC &#39;An entry which represents a ship&#39;