Return-Path: X-Original-To: apmail-directory-commits-archive@www.apache.org Delivered-To: apmail-directory-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 40E1FD7EC for ; Tue, 4 Dec 2012 11:14:59 +0000 (UTC) Received: (qmail 17135 invoked by uid 500); 4 Dec 2012 11:14:59 -0000 Delivered-To: apmail-directory-commits-archive@directory.apache.org Received: (qmail 17089 invoked by uid 500); 4 Dec 2012 11:14:59 -0000 Mailing-List: contact commits-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@directory.apache.org Delivered-To: mailing list commits@directory.apache.org Received: (qmail 17078 invoked by uid 99); 4 Dec 2012 11:14:58 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 11:14:58 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Dec 2012 11:14:54 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 0AAF623889BF for ; Tue, 4 Dec 2012 11:14:33 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r840701 - in /websites/staging/directory/trunk/content: ./ api/user-guide/ images/ Date: Tue, 04 Dec 2012 11:14:31 -0000 To: commits@directory.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20121204111433.0AAF623889BF@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Tue Dec 4 11:14:26 2012 New Revision: 840701 Log: Staging update by buildbot for directory Added: websites/staging/directory/trunk/content/api/user-guide/4.1-schema-manager.html websites/staging/directory/trunk/content/images/SchemaObjects.png (with props) Modified: websites/staging/directory/trunk/content/ (props changed) websites/staging/directory/trunk/content/api/user-guide/2-basic-ldap-api-usage.html websites/staging/directory/trunk/content/api/user-guide/3-advanced-ldap-api-usage.html websites/staging/directory/trunk/content/api/user-guide/4-schema-management.html websites/staging/directory/trunk/content/api/user-guide/5-ldap-security.html websites/staging/directory/trunk/content/api/user-guide/6-ldap-data-structures.html websites/staging/directory/trunk/content/api/user-guide/7-ldap-rfcs.html Propchange: websites/staging/directory/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Tue Dec 4 11:14:26 2012 @@ -1 +1 @@ -1416877 +1416887 Modified: websites/staging/directory/trunk/content/api/user-guide/2-basic-ldap-api-usage.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide/2-basic-ldap-api-usage.html (original) +++ websites/staging/directory/trunk/content/api/user-guide/2-basic-ldap-api-usage.html Tue Dec 4 11:14:26 2012 @@ -130,7 +130,7 @@

We provide three different set of methods to send requests to the LDAP server : A first set which is the simplest, where the methods don't return a response, except the search and compare methods A second set, for advanced users, giving full control to the user * A third set allowing the user to send asynchronous requests.

-

Content

+

Contents

  • Connection and disconnection
  • Binding and unbinding (...)
    • Modified: websites/staging/directory/trunk/content/api/user-guide/3-advanced-ldap-api-usage.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide/3-advanced-ldap-api-usage.html (original) +++ websites/staging/directory/trunk/content/api/user-guide/3-advanced-ldap-api-usage.html Tue Dec 4 11:14:26 2012 @@ -127,7 +127,7 @@

    3 - Advanced LDAP API Usage (...)

    -

    Content

    +

    Contents

    • Controls (...)
    • Extended operations (e)
      • Modified: websites/staging/directory/trunk/content/api/user-guide/4-schema-management.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide/4-schema-management.html (original) +++ websites/staging/directory/trunk/content/api/user-guide/4-schema-management.html Tue Dec 4 11:14:26 2012 @@ -127,9 +127,9 @@

      4 - Schema Management (...)

      -

      Content

      +

      Contents

        -
      • SchemaManager (e)
        • +
      • SchemaManager (...)
      • AttributeTypes (e)
      • [DITContentRules (e)(4.3-dit-content-rules.html)
      • [DITStructureRules (e)(4.4-dit-structure-rules.html)
        • Added: websites/staging/directory/trunk/content/api/user-guide/4.1-schema-manager.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide/4.1-schema-manager.html (added) +++ websites/staging/directory/trunk/content/api/user-guide/4.1-schema-manager.html Tue Dec 4 11:14:26 2012 @@ -0,0 +1,214 @@ + + + + + 4.1 - Schema Manager — Apache Directory + + + + + + +
        + +
        +
        + + + +
        +
        + + +
        +
        + + 4 - Schema Management + +
        +
        + + 4 - Schema Management + +
        +
        + + 4.2 - AttributeTypes + +
        +
        +
        + + +

        4.1 - Schema Manager (...)

        +

        Apache DS has to keep the schema elements available from all the parts of the server. This is done through what we call the SchemaManager. It hides all the internal structure from the users.

        +

        Description

        +

        The SchemaManager stores all the Schema elements (AttributeTypes (e), ObjectClasses (e), ... Internally, we store those elements into the Registries, which are hives where each Schema Objects are stored.

        +

        From the user point of view, the SchemaManager is seen as a representation of the available schemas. It can of course be extended, or modified, by adding or removing some schema elements.

        +

        The server has one instance of a SchemaManager, which is used internally, and a user won't control it, in any case. On the client side, we can load a SchemaManager either from the server (and then we have a duplicated instance), or from existing schema files. We can even create a brand new SchemaManager and fill it with all what we need.

        +

        Contents

        +

        The SchemaManager stores all the 11 kind of schema elements :

        + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
        Name
        ObjectClasses (e)
        AttributeTypes (...)
        Syntaxes (e)
        MatchingRules (e)
        DITContentRules (e)
        DITStructureRules (e)
        NameForms (e)
        MatchingRuleUses (e)
        SyntaxChecker (e)
        Normalizer (e)
        LdapComparator (e)
        +

        The last three elements are ApacheDS specific.

        +

        All those elements have some tight relationships. The following schema expose all the relations between all those elements :

        +

        +

        Using a SchemaManager

        +

        ...

        + + +
        +
        + + 4 - Schema Management + +
        +
        + + 4 - Schema Management + +
        +
        + + 4.2 - AttributeTypes + +
        +
        +
        + + +
        +
        +
        + +
        + + \ No newline at end of file Modified: websites/staging/directory/trunk/content/api/user-guide/5-ldap-security.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide/5-ldap-security.html (original) +++ websites/staging/directory/trunk/content/api/user-guide/5-ldap-security.html Tue Dec 4 11:14:26 2012 @@ -127,7 +127,7 @@

        5 - LDAP Security (...)

        -

        Content

        +

        Contents

        • 5.1 - ACI and ACLs (e)
        • 5.2 - SSL (e)
          • Modified: websites/staging/directory/trunk/content/api/user-guide/6-ldap-data-structures.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide/6-ldap-data-structures.html (original) +++ websites/staging/directory/trunk/content/api/user-guide/6-ldap-data-structures.html Tue Dec 4 11:14:26 2012 @@ -127,7 +127,7 @@

          6 - LDAP Data Structures (...)

          -

          Content

          +

          Contents

          • 6.1 - AdministrativePoint (e)
          • 6.2 - AdministrativeRole (e)
            • Modified: websites/staging/directory/trunk/content/api/user-guide/7-ldap-rfcs.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide/7-ldap-rfcs.html (original) +++ websites/staging/directory/trunk/content/api/user-guide/7-ldap-rfcs.html Tue Dec 4 11:14:26 2012 @@ -129,7 +129,6 @@

            7 - LDAP Related RFCs

            LDAP and X.500 are specified through many RFCs. Here is the list of available RFCs within some category (there are around 100 RFCs available, some of them are now deprecated, some other are obsolete.

            This page list all the existing RFCs, obsolete or not.

            -

            : Informational

            : Informational

            : Historic

            : Proposed Standard

            Added: websites/staging/directory/trunk/content/images/SchemaObjects.png ============================================================================== Binary file - no diff available. Propchange: websites/staging/directory/trunk/content/images/SchemaObjects.png ------------------------------------------------------------------------------ svn:mime-type = image/png