Author: buildbot Date: Fri Nov 2 06:58:00 2012 New Revision: 836982 Log: Staging update by buildbot for directory Added: websites/staging/directory/trunk/content/api/java-api.html websites/staging/directory/trunk/content/api/user-guide/ websites/staging/directory/trunk/content/api/user-guide.html websites/staging/directory/trunk/content/api/user-guide/1-introduction.html websites/staging/directory/trunk/content/api/vision.html Modified: websites/staging/directory/trunk/content/ (props changed) websites/staging/directory/trunk/content/api/groovy-ldap.html Propchange: websites/staging/directory/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Fri Nov 2 06:58:00 2012 @@ -1 +1 @@ -1404286 +1404885 Modified: websites/staging/directory/trunk/content/api/groovy-ldap.html ============================================================================== --- websites/staging/directory/trunk/content/api/groovy-ldap.html (original) +++ websites/staging/directory/trunk/content/api/groovy-ldap.html Fri Nov 2 06:58:00 2012 @@ -17,7 +17,7 @@ --> - Five Minutes Tutorial — Apache Directory + Groovy LDAP — Apache Directory Added: websites/staging/directory/trunk/content/api/java-api.html ============================================================================== --- websites/staging/directory/trunk/content/api/java-api.html (added) +++ websites/staging/directory/trunk/content/api/java-api.html Fri Nov 2 06:58:00 2012 @@ -0,0 +1,176 @@ + + + + + LDAP Java API — Apache Directory + + + + + + +
+ +
+
+ + + +
+
+ + + +

LDAP Java API

+

This is the Java implementation of a new LDAP API. This effort was initially conducted with the OpenDS team.

+

Background

+

There are a few existing LDAP API around there. Here is a short list and description.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
APIVersionLicenseDescription
Apache Directory Client API1.0-M13ASL 2.0The Apache Directory Server CLient API.
jLDAP2008_03-01-1OpenLDAP Public LicenseA Novell contribution to the OpenLDAP project
JNDI1.2Sun licenseThis is not a pure LDAP API, however it's included in J2SE since Java 5. Probably the API selected by many developers
ldapSDK4.17Netscape Public LicenseThe Mozilla API, formally the Netscape LDAP API
OpenDS client APIN/ACDDLThe OpenDS API
UnboundID API0.9.10GPLv2A new API developed by the UnboundID company
+

(There may be some more we don't know about)

+

Features

+

The User Guide pages gives the list of features the API provides.

+ + + +
+
+
+ +
+ + \ No newline at end of file Added: websites/staging/directory/trunk/content/api/user-guide.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide.html (added) +++ websites/staging/directory/trunk/content/api/user-guide.html Fri Nov 2 06:58:00 2012 @@ -0,0 +1,227 @@ + + + + + Users Guide — Apache Directory + + + + + + +
+ +
+
+ + + +
+
+ + + +

Users guide

+

+Work in progress

+

This is a very preliminary version...

+

Pages with a (e) at the end of the title are empty pages +Pages with a (...) ate the end of the title are not completed yet +Other pages are finished (but may be reviewed) +

+

This documentation is about the newly LDAP API developped at the Apache Software Foundation. We expect this API will be a replacement for all the ancient API (jLdap, Mozilla LDAP SDK and JNDI).

+

About this guide

+

Getting started. Learn how to use the LDAP API, connect to various LDAP server, manipulate the data within your directory.

+

Audience

+

This guide is primarily for people new to the LDAP API. If you plan to use the API as is, maybe even for your first LDAP experience, you'll (hopefully) find all information necessary to do so. Only basic tasks are covered. Learn more about the options you have (and many other things) in the [Advanced User's Guide].

+

Feedback welcome!

+

We are quite interested to improve the content of this guide. Feel free to provide us feedback: +!email.png! mailto:users@directory.apache.org

+

Table of contents

+
    +
  • +

    1 - Introduction

    +

    Java and LDAP +LDAP in a few words +The Apache LDAP API rational +Preparation to code

    +
  • +
+

Basic LDAP API usage (...)

+
Connection and disconnection
+Binding and unbinding (...)
+Searching (...)
+Adding entries
+Deleting entries
+Modifying entries (e)
+Moving an renaming entries (e)
+Comparing entries (e)
+Exception management (...)
+
+ + +

Advanced LDAP API usage (...)

+
Controls (...)
+Extended operations (e)
+Referrals (e)
+Aliases (e)
+LDIF, DSML (...)
+Abandonning an operation (e)
+Server informations (e)
+
+ + +

SchemaManagement (...)

+
SchemaManager (...)
+AttributeTypes (e)
+ObjectClasses (e)
+MatchingRules (e)
+Syntaxes (e)
+NameForms (e)
+DITContentRules (e)
+DITStructureRules (e)
+MatchingRuleUses (e)
+
+ + +

LDAP security (e)

+
ACI and ACLs (e)
+SSL (e)
+StartTLS (e)
+
+ + +

LDAP data structures (...)

+
Entry
+Attribute
+Dn
+Rdn
+Ava
+Value
+Modification
+LdifEntry
+LdifControl (e)
+Oid
+Csn
+ObjectClass (e)
+NameForm (e)
+Message (...)
+LdapResult
+Referral (e)
+Node (e)
+LdapUrl (...)
+Cursor (e)
+AdministrativePoint (e)
+Refinment (e)
+SubtreeSpecification (e)
+AttributeType (...)
+DITContentRule (e)
+DITStructureRule (e)
+LdapSyntax (e)
+LdapComparator (e)
+Normalizer (e)
+SyntaxChecker (e)
+MatchingRule (e)
+MatchingRuleUse (e)
+
+ + +

LDAP related RFCs

+ + + +
+
+
+ +
+ + \ No newline at end of file Added: websites/staging/directory/trunk/content/api/user-guide/1-introduction.html ============================================================================== --- websites/staging/directory/trunk/content/api/user-guide/1-introduction.html (added) +++ websites/staging/directory/trunk/content/api/user-guide/1-introduction.html Fri Nov 2 06:58:00 2012 @@ -0,0 +1,162 @@ + + + + + 1 - Introduction — Apache Directory + + + + + + +
+ +
+
+ + + +
+
+ + + + + +

1 - Introduction

+

This User Guide goal is to provide some clue for any developer wanting to use the LDAP API. We have mixed some description of each important features with some tested snippet of code (all of them has been integrated as tests in the API code).

+

We hope it will be enough for you to quickly get started, but in any case, if you feel like improving this document, feel free to post your suggestion to the Apache Directory mailing list : any contribution is welcomed !

+ + + + + +
+
+
+ +
+ + \ No newline at end of file Added: websites/staging/directory/trunk/content/api/vision.html ============================================================================== --- websites/staging/directory/trunk/content/api/vision.html (added) +++ websites/staging/directory/trunk/content/api/vision.html Fri Nov 2 06:58:00 2012 @@ -0,0 +1,128 @@ + + + + + LDAP API - Vision — Apache Directory + + + + + + +
+ +
+
+ + + +
+
+ + + +

Vision

+

When we started to work on replication implementation, we needed a client API in order to communicate using the LDAP protocol with remote LDAP servers. We could have used some existing LDAP API, but as we have already defined a lot of base classes we would have had to convert back and forth, we thought it would be better to build the missing pieces and define our own complete LDAP API.

+

This is one of the reasons we started this sub-project.

+

Another reason is that we worked with Sun a few years ago to draw a new version of JNDI, an aborted effort, sadly. We also have been contacted by the OpenLDAP team as they wanted to know if we were ready to maintain jLDAP, as it needed some patches, and as they didn't have enough workforce to do so. Last, not least, OpenDS team is also interested to see if we can avoid duplication of efforts, as they are also defining an LDAP API.

+

All those events make it interesting to try to find a common way to define a new LDAP API, gathering the interest of the largest developer base possible.

+

As we have not finished to implement all the needed features, it's easy for us to try to figure which parts can be shared with other projects, and which parts must be configurable. A clear example is the underlying network layer: OpenDS will use Grizzly, while we will use MINA. This should be transparent for developers.

+

Last, not least, no one can claim to be better than all the other great people out there, and claim to be able to define the best possible API. We at The ASF believe that collaboration within a community is better than working alone. We are pleased to share what we have already done, ready to move forward in better directions if it allows the API to be more reliable, usable and at the end, easier to use for devlopers.

+ + + +
+
+
+ +
+ + \ No newline at end of file