directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From anto...@apache.org
Subject svn commit: r1425812 - in /directory/site/trunk/content: apacheds/advanced-ug/3.1-administrative-points.mdtext apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.mdtext apacheds/basic-ug/1.1-what-apacheds-is.mdtext vision.mdtext
Date Wed, 26 Dec 2012 04:02:43 GMT
Author: antoine
Date: Wed Dec 26 04:02:43 2012
New Revision: 1425812

URL: http://svn.apache.org/viewvc?rev=1425812&view=rev
Log:
further updates

Modified:
    directory/site/trunk/content/apacheds/advanced-ug/3.1-administrative-points.mdtext
    directory/site/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.mdtext
    directory/site/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.mdtext
    directory/site/trunk/content/vision.mdtext

Modified: directory/site/trunk/content/apacheds/advanced-ug/3.1-administrative-points.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/advanced-ug/3.1-administrative-points.mdtext?rev=1425812&r1=1425811&r2=1425812&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/advanced-ug/3.1-administrative-points.mdtext (original)
+++ directory/site/trunk/content/apacheds/advanced-ug/3.1-administrative-points.mdtext Wed
Dec 26 04:02:43 2012
@@ -67,9 +67,9 @@ Those three different *APs* are related 
 * *AAPs* manage an *AA* as if all the possible type of *SAP* where declared
 for this area
 * *SAPs* manage an *AA* with respect to one specific kind of role (Access
-Control, Collective Attributes, SubSchema or Trigger Execution )
+Control, Collective Attributes, SubSchema or Trigger Execution)
 * IAPs manage an *AA* inside another *AP*
-* An *AAP* or a *SAP* start at some point in the tree, and all the entries
+* An *AAP* or a *SAP* starts at some point in the tree, and all the entries
 below this *AAP*/*SAP* aren't related to any other *AAP*. That also means
 that if an *AAP*/*SAP* is created below an existing AP, then all the
 entries it covers are unlinked from the previous AP (except that for *SAP*,

Modified: directory/site/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.mdtext?rev=1425812&r1=1425811&r2=1425812&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.mdtext
(original)
+++ directory/site/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.mdtext
Wed Dec 26 04:02:43 2012
@@ -24,6 +24,7 @@ Notice: Licensed to the Apache Software 
 
 # Operations
 There are six kind of operations we can have on an AdministrativePoint :
+
 * creating a new AP
 * removing an existing AP
 * modifying an existing AP by adding or removing a role
@@ -86,6 +87,7 @@ with each of those modifications one by 
 ### Addition of roles
 For this modification, we will have to check for each of the roles the very
 same elements than for the Add operation above :
+
 * if the entry does not have an AdministrativeRole AT, we have to create it
 * we must have at least one value
 * the role must be syntaxicaly correct
@@ -101,7 +103,7 @@ following modification fails.
 ### Removing of roles
 First, if there is no value for this modification, then that means we must
 delete the Attribute. This case will be analyzed later.
-For each of the role to remove, we have to apply those checks :
+For each of the roles to remove, we have to apply those checks :
 * the role must be syntaxicaly correct
 * it must already exist into the attribute
 * we can't remove an AAP or a SAP if there is a direct IAP in one of its

Modified: directory/site/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.mdtext?rev=1425812&r1=1425811&r2=1425812&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.mdtext Wed Dec 26
04:02:43 2012
@@ -30,13 +30,13 @@ This section describes what Apache Direc
 
 ## System vision
 
-ApacheDS 1.5 is an embeddable, extendable, standards compliant, modern LDAP server written
entirely in Java, and available under the Apache Software License. Other network protocols
like Kerberos and NTP are supported as well (and even more may be added), but basically (and
especially for this introduction guide) ApacheDS is an LDAP server.
+ApacheDS 2.0 is an embeddable, extendable, standards compliant, modern LDAP server written
entirely in Java, and available under the Apache Software License. Other network protocols
like Kerberos and NTP are supported as well (and even more may be added), but basically (and
especially for this introduction guide) ApacheDS is an LDAP server.
 
 _Embeddable_ means that it is possible to configure, start and stop ApacheDS from other Java
components, especially application servers, and the server runs within the same VM. The solution
has already been successfully embedded in Apache Geronimo, JBoss, and others. The fact that
the server is embeddable is quite interesting, nevertheless you also have the deployment option
to run the server standalone, for instance as a Windows service. Perhaps you know this situation
from other LDAP servers -- open source (like OpenLDAP) as well as commercial ones (like Sun
Java System Directory Server). This guide is dedicated to people that are new to ApacheDS.
 The guide concentrates on installing, configuring and running ApacheDS in a standalone configuration.
 
 _Extendable_ means that the modern architecture of the solution provides many extension points.
Write your own partitions to store directory data, interceptors to add functionality, etc.
by implementing certain interfaces and plugging them in using Spring.
 
-_Standard compliant_ means that ApacheDS 1.5 adheres to all RFCs relevant to LDAPv3. Please
note that version 1.0 of the server has been successfully certified by the Open Group in September
2006 ("LDAP certified"). Thus LDAP clients may rightly expect that ApacheDS behaves like they
expect.
+_Standard compliant_ means that ApacheDS 2.0 adheres to all RFCs relevant to LDAPv3. Please
note that version 1.0 of the server has been successfully certified by the Open Group in September
2006 ("LDAP certified"). Thus LDAP clients may rightly expect that ApacheDS behaves like they
expect.
 
 _Modern_ means that ApacheDS aims modernize the LDAP territory, as well as it favors standards
compliance. New rich integration tier constructs like LDAP Stored Procedures and Triggers
are being built on top of existing standards.
 
@@ -50,11 +50,11 @@ _Entirely written in Java_ means that th
 
 Through his experiences with enterprise LDAP directories, Alex Karasulu, realized there is
a great need for rich integration tier constructs like LDAP Stored Procedures, Triggers, and
Views.  In 2001 he set out to alter the OpenLDAP server to offer support for these useful
facilities which are present in relational databases but missing in the LDAP world.  Alex's
attempts failed due to the complexity of the software which was brittle, and difficult to
manage.  As C code ported to several platforms, the OpenLDAP code base, had several #IFDEF
conditional pre-compiler directives that made it difficult to change the code.  At this point
Alex thought about implementing a new LDAP server in pure Java.  Thanks to NIO this was finally
possible using the 1.4 JDK. 
 
-In October 2002 Alex Karasulu founded and registered the [LDAPd|http://sourceforge.net/projects/ldapd]
project at SourceForge.net.  LDAPd was a a pure Java embeddable LDAP v3 protocol daemon built
on the Avalon framework.  Alex donated the code to the Apache Software Foundation and the
code entered the [Apache Incubator|http://incubator.apache.org/|Apache Incubator Homepage]
in October 2003.  One year later in October of 2004, the Apache Directory Top Level Project
(TLP) was formed after a successful incubation with the now called Apache Directory Server
as its flagship product. After 4 years of development, in October 2006, Apache Directory Server
1.0 was released as an Open Group certified LDAPv3 protocol server. The certification has
been renewed in September 2007.
+In October 2002 Alex Karasulu founded and registered the [LDAPd](http://sourceforge.net/projects/ldapd)
project at SourceForge.net.  LDAPd was a a pure Java embeddable LDAP v3 protocol daemon built
on the Avalon framework.  Alex donated the code to the Apache Software Foundation and the
code entered the [Apache Incubator](http://incubator.apache.org/) in October 2003.  One year
later in October of 2004, the Apache Directory Top Level Project (TLP) was formed after a
successful incubation with the now called Apache Directory Server as its flagship product.
After 4 years of development, in October 2006, Apache Directory Server 1.0 was released as
an Open Group certified LDAPv3 protocol server. The certification has been renewed in September
2007.
 
 Having a standards compliant and modern LDAP server, Apache Directory Team is now working
on Identity and Access Management solutions leveraging the directory technology.
 
 ## Resources
 
-* [Proposal for an Apache Directory Project](http://directory.apache.org/community%26resources/proposal-for-an-apache-directory-project.html)
the original proposal for incubation, September 2003.
-* [Architecting the Modern LDAP Renaissance: The Apache Directory Vision](http://directory.apache.org/community%26resources/ldap-renaissance.html),
Paper for 1st International Conference on LDAP, September 2007.
\ No newline at end of file
+* [Proposal for an Apache Directory Project](../../original-project-proposal.html) the original
proposal for incubation, September 2003.
+* [Architecting the Modern LDAP Renaissance: The Apache Directory Vision](../../vision.html),
Paper for 1st International Conference on LDAP, September 2007.
\ No newline at end of file

Modified: directory/site/trunk/content/vision.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/vision.mdtext?rev=1425812&r1=1425811&r2=1425812&view=diff
==============================================================================
--- directory/site/trunk/content/vision.mdtext (original)
+++ directory/site/trunk/content/vision.mdtext Wed Dec 26 04:02:43 2012
@@ -20,6 +20,7 @@ Notice: Licensed to the Apache Software 
 
 by Alex Karasulu, Founder of the [Apache Directory Project](http://directory.apache.org),
October 2002
 This paper was later, in September 2007, submitted to and accepted by the [1st International
Conference on LDAP](http://www.guug.de/veranstaltungen/ldapcon2007/), Cologne (Germany)
+
 [TOC]
 
 ## Abstract



Mime
View raw message