directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1839899 - in /directory/site/trunk: content/api/news.mdtext content/api/user-guide/4.2-schema-manager.mdtext content/index.mdtext lib/
Date Sun, 02 Sep 2018 23:53:25 GMT
Author: elecharny
Date: Sun Sep  2 23:53:25 2018
New Revision: 1839899

Updated the web site for Apache LDAP API 2.0.0.AM2


Modified: directory/site/trunk/content/api/news.mdtext
--- directory/site/trunk/content/api/news.mdtext (original)
+++ directory/site/trunk/content/api/news.mdtext Sun Sep  2 23:53:25 2018
@@ -1,3 +1,27 @@
+# News 
+<h2 class="news">Apache Directory LDAP API 2.0.0.AM2 released <em>posted on September
3rd, 2018</em></h2>
+The Apache Directory Team is proud to announce the availability of version 2.0.0.AM2 of the
Apache Directory LDAP API.
+The Apache Directory LDAP API is an ongoing effort to provide an enhanced LDAP API, as a
replacement for JNDI and the existing LDAP API (jLdap and Mozilla LDAP API).
+This is a schema aware API, with some convenient ways to access a LDAP server. This API is
not only targeting the Apache Directory Server, but should work pristine with any LDAP server.
+It's also an extensible API : new Controls, schema elements and network layer could be added
or used in the near future. It's also OSGi capable.
+This is a bug fix release that address a performance issue with the schema: All the SchemaObjects
had their hashcode set to 0, which made it
+slow to fetch from a Map or a Set. That impacted Studio startup, making it slow when a user
has several connections.
+A couple of other issues have also been fixed.
+Here are the associated JIRA tickets :
+DIRAPI-318, Schema elements HashCode are not computed at all
+DIRAPI-319, The RestrictedByItem class stores elements in a Set, expecting it to be ordered.
+DIRAPI-291, The Immutable schema object can't be used
+Downloads are available [here](downloads.html) and the User's Guide is [there](user-guide.html)
 # CVE-2018-1337: Plaintext Password Disclosure in Secured Channel
 The Apache LDAP API 1.0.2 that has just been released fix a [critical security issue](
A bug in the way the SSL Filter was setup made it possible for another thread to use the connection
before the TLS layer has been established, if the connection has already been used and put
back in a pool of connections, leading to leaking any information contained in this request
(including the credentials when sending a BIND request)
@@ -7,6 +31,7 @@ We urge you to switch to this version.
 Downloads are available [here](downloads.html)
 # News
 <h2 class="news">Apache Directory LDAP API 1.0.2 released <em>posted on June
6st, 2018</em></h2>

Modified: directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext
--- directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext Sun Sep  2 23:53:25
@@ -47,8 +47,8 @@ The API and the ApacheDS server componen
 The **SchemaManager** stores all the Schema elements (**[AttributeTypes (e)]()**, **[ObjectClasses
(e)]()**, ... Internally, we store these elements into what is call a **Registries**.  Registries
are hives where each Schema Object is stored. Each schema element has a dedicated **Registry**
associated with it. Think of it as a Map which returns a reference to a specific Schema Element
according to its name or OID.
     Note : 
-    each Schema Element is properly defined by one of its names or OID. The OID must be unique
across all schema elements, 
-    when the name can be used in different schema element (for instance, the **audio** AttributeType
or ObjectClass)
+    Each Schema Element is properly defined by one of its names or <b>OID</b>.
The <b>OID</b> must be unique across all schema elements, 
+    when the name can be used in different schema element (for instance, the <b>audio</b>
<b>AttributeType</b> or <b>ObjectClass</b>)
 From the user point of view, the **SchemaManager** is seen as a representation of the available
LDAP schema elements. It can of course be extended, or modified, by adding or removing schema
elements. For historic reasons, the schema elements are gathered into what we call a **schema**.
Usually, this is what you load into a **schemaManager**

Modified: directory/site/trunk/content/index.mdtext
--- directory/site/trunk/content/index.mdtext (original)
+++ directory/site/trunk/content/index.mdtext Sun Sep  2 23:53:25 2018
@@ -67,7 +67,7 @@ td {font-size: 12px;}
         <div class="download-link">
-          <a href="./../api/downloads.html" class="download_badge_api"><b>Download
Apache<br>LDAP API 2.0.0.AM1</b></a>
+          <a href="./../api/downloads.html" class="download_badge_api"><b>Download
Apache<br>LDAP API 2.0.0.AM2</b></a>
         <div class="separator">&nbsp;</div>

Modified: directory/site/trunk/lib/
--- directory/site/trunk/lib/ (original)
+++ directory/site/trunk/lib/ Sun Sep  2 23:53:25 2018
@@ -2,7 +2,7 @@ package path;
 # Versions (for download links)
 our $version_api = "1.0.2";
-our $version_api2 = "2.0.0.AM1";
+our $version_api2 = "2.0.0.AM2";
 our $version_apacheds = "2.0.0.AM25";
 our $version_studio = "2.0.0.v20170904-M13";
 our $version_studio_name = "2.0.0-M13";

View raw message