directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r957126 [18/18] - in /websites/staging/directory/trunk/content: ./ apacheds/ apacheds/advanced-ug/ apacheds/basic-ug/ apacheds/configuration/ apacheds/kerberos-ug/ api/ api/download/ api/groovy-api/ api/user-guide/ escimo/ fortress/ fortres...
Date Sun, 05 Jul 2015 22:34:38 GMT
Modified: websites/staging/directory/trunk/content/studio/download-old-versions.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/download-old-versions.html (original)
+++ websites/staging/directory/trunk/content/studio/download-old-versions.html Sun Jul  5 22:34:35 2015
@@ -151,7 +151,18 @@
 
 
 
-<h1 id="download-old-versions">Download Old Versions</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="download-old-versions">Download Old Versions<a class="headerlink" href="#download-old-versions" title="Permanent link">&para;</a></h1>
 <p><center></p>
 <table>
 <thead>
@@ -302,7 +313,7 @@
 <li>the MD5 file (checksum).</li>
 </ul>
 </blockquote>
-<h2 id="verify-the-integrity-of-the-file">Verify the integrity of the file</h2>
+<h2 id="verify-the-integrity-of-the-file">Verify the integrity of the file<a class="headerlink" href="#verify-the-integrity-of-the-file" title="Permanent link">&para;</a></h2>
 <p>The PGP signatures can be verified using PGP or GPG. First download the <a href="http://www.apache.org/dist/directory/KEYS">KEYS file</a> as well as the asc signature file for the relevant distribution. Then verify the signatures using:</p>
 <div class="codehilite"><pre>$ <span class="n">pgpk</span> <span class="o">-</span><span class="n">a</span> <span class="n">KEYS</span>
 $ <span class="n">pgpv</span> <span class="n">apache_1</span><span class="p">.</span>3<span class="p">.</span>24<span class="p">.</span><span class="n">tar</span><span class="p">.</span><span class="n">gz</span><span class="p">.</span><span class="n">asc</span>

Modified: websites/staging/directory/trunk/content/studio/downloads.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/downloads.html (original)
+++ websites/staging/directory/trunk/content/studio/downloads.html Sun Jul  5 22:34:35 2015
@@ -151,9 +151,20 @@
 
 
 
-<h1 id="downloads">Downloads</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="downloads">Downloads<a class="headerlink" href="#downloads" title="Permanent link">&para;</a></h1>
 <p>Apache Directory Studio is a complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with the ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins, that can be easily upgraded with additional ones. These plugins can even run within Eclipse itself. </p>
-<h2 id="apache-directory-studio-rcp-application">Apache Directory Studio RCP Application</h2>
+<h2 id="apache-directory-studio-rcp-application">Apache Directory Studio RCP Application<a class="headerlink" href="#apache-directory-studio-rcp-application" title="Permanent link">&para;</a></h2>
 <p>Apache Directory Studio is a multi-platform application and runs on Mac OS X, Linux and Windows.</p>
 <p>Please select the download corresponding to your operating system:</p>
 <ul>
@@ -167,13 +178,13 @@
 <p><img alt="Download" src="../images/download-windows.png" /> <a href="download/download-windows.html">Download for Windows</a></p>
 </li>
 </ul>
-<h2 id="plugins-for-eclipse">Plugins for Eclipse</h2>
+<h2 id="plugins-for-eclipse">Plugins for Eclipse<a class="headerlink" href="#plugins-for-eclipse" title="Permanent link">&para;</a></h2>
 <p>You can also install plugins for Eclipse using our update site (requires Java 7 or newer and Eclipse 4.2 (Juno) or newer).</p>
 <p>The URL of our update site is <strong><a href="http://directory.apache.org/studio/update">http://directory.apache.org/studio/update</a></strong></p>
 <p>Learn how to <a href="installation-in-eclipse.html">install Apache Directory Studio plugins in Eclipse</a> <a href="installation-in-eclipse.html"><img alt="Download" src="../images/download-eclipse.png" /></a></p>
-<h2 id="sources">Sources</h2>
+<h2 id="sources">Sources<a class="headerlink" href="#sources" title="Permanent link">&para;</a></h2>
 <p>The sources of Apache Directory Studio and its plugins are available <a href="download/download-sources.html">here</a> <a href="download/download-sources.html"><img alt="Download" src="../images/download-sources.png" /></a>.</p>
-<h2 id="old-versions">Old Versions</h2>
+<h2 id="old-versions">Old Versions<a class="headerlink" href="#old-versions" title="Permanent link">&para;</a></h2>
 <p>You can download old versions of Apache Directory Studio (or Apache LDAP Studio) <a href="download-old-versions.html">here</a>.</p>
 
 

Modified: websites/staging/directory/trunk/content/studio/faqs.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/faqs.html (original)
+++ websites/staging/directory/trunk/content/studio/faqs.html Sun Jul  5 22:34:35 2015
@@ -151,6 +151,17 @@
 
 
 
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
 <h1>FAQs</h1>
 
 <div class="toc">
@@ -162,7 +173,7 @@
 <li><a href="#location-of-apache-directory-studio-settings">Location of Apache Directory Studio settings</a></li>
 </ul>
 </div>
-<h3 id="how-to-set-the-language-of-studio">How to set the language of Studio?</h3>
+<h3 id="how-to-set-the-language-of-studio">How to set the language of Studio?<a class="headerlink" href="#how-to-set-the-language-of-studio" title="Permanent link">&para;</a></h3>
 <p>Studio currentlly is translated in three languages: English (en), French (fr) and German (de). When starting Studio, the language setting of your operation system is used to determine the language of Studio (On linux, the LC_CTYPE environment variable is used to determinate the default language). </p>
 <p>However it is possible to force another language:</p>
 <ul>
@@ -195,10 +206,10 @@
 </li>
 </ul>
 <p>Please notice the line break between -nl and the language.</p>
-<h3 id="when-browsing-and-expanding-an-entry-studio-only-shows-1000-child-entries">When browsing and expanding an entry, Studio only shows 1000 child entries.</h3>
+<h3 id="when-browsing-and-expanding-an-entry-studio-only-shows-1000-child-entries">When browsing and expanding an entry, Studio only shows 1000 child entries.<a class="headerlink" href="#when-browsing-and-expanding-an-entry-studio-only-shows-1000-child-entries" title="Permanent link">&para;</a></h3>
 <p>Studio uses a client-side count limit when browsing the DIT. This limit is defined in the connection properties. See
 <a href="./users-guide/ldap_browser/tools_connection_properties.html#tools_connection_properties_browser_options">Connection Properties</a> how to change it. </p>
-<h3 id="how-to-set-the-java-vm-to-use">How to set the Java VM to use?</h3>
+<h3 id="how-to-set-the-java-vm-to-use">How to set the Java VM to use?<a class="headerlink" href="#how-to-set-the-java-vm-to-use" title="Permanent link">&para;</a></h3>
 <ul>
 <li>
 <p>The first option is to start Apache Directory Studio with the following command line parameters:</p>
@@ -229,7 +240,7 @@
 </li>
 </ul>
 <p>Please notice the line break between -vm and the path.</p>
-<h3 id="how-to-increase-the-heap-memory">How to increase the heap memory?</h3>
+<h3 id="how-to-increase-the-heap-memory">How to increase the heap memory?<a class="headerlink" href="#how-to-increase-the-heap-memory" title="Permanent link">&para;</a></h3>
 <ul>
 <li>
 <p>The first option is to start Apache Directory Studio with the following command line parameters:</p>
@@ -265,7 +276,7 @@
 </li>
 </ul>
 <p>Please notice the line breaks.</p>
-<h3 id="location-of-apache-directory-studio-settings">Location of Apache Directory Studio settings</h3>
+<h3 id="location-of-apache-directory-studio-settings">Location of Apache Directory Studio settings<a class="headerlink" href="#location-of-apache-directory-studio-settings" title="Permanent link">&para;</a></h3>
 <p>The settings are located per default in your home directory under the directory <em>.ApacheDirectoryStudio</em>.</p>
 <p>The file containing all connections is:</p>
 <div class="codehilite"><pre><span class="o">~/</span><span class="p">.</span><span class="n">ApacheDirectoryStudio</span><span class="o">/</span><span class="p">.</span><span class="n">metadata</span><span class="o">/</span><span class="p">.</span><span class="n">plugins</span><span class="o">/</span><span class="n">org</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">directory</span><span class="p">.</span><span class="n">studio</span><span class="p">.</span><span class="n">connection</span><span class="p">.</span><span class="n">core</span><span class="o">/</span><span class="n">connections</span><span class="p">.</span><span class="n">xml</span>

Modified: websites/staging/directory/trunk/content/studio/index.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/index.html (original)
+++ websites/staging/directory/trunk/content/studio/index.html Sun Jul  5 22:34:35 2015
@@ -238,7 +238,18 @@
     
 
     
-        <div class="news"><h1 id="news">News</h1>
+        <div class="news"><style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="news">News<a class="headerlink" href="#news" title="Permanent link">&para;</a></h1>
 <h2 class="news">Apache Directory Studio 2.0-0-M9 released <em>posted on June 11th, 2015</em></h2>
 
 <p>The Apache Directory Team is pleased to announce the release of Apache Directory Studio 2.0.0-M9, the ninth milestone release of the version 2.0 of its Eclipse based LDAP Browser and Directory client.</p>

Modified: websites/staging/directory/trunk/content/studio/installation-in-eclipse.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/installation-in-eclipse.html (original)
+++ websites/staging/directory/trunk/content/studio/installation-in-eclipse.html Sun Jul  5 22:34:35 2015
@@ -151,7 +151,18 @@
 
 
 
-<h1 id="installing-apache-directory-studio-in-eclipse">Installing Apache Directory Studio in Eclipse</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="installing-apache-directory-studio-in-eclipse">Installing Apache Directory Studio in Eclipse<a class="headerlink" href="#installing-apache-directory-studio-in-eclipse" title="Permanent link">&para;</a></h1>
 <blockquote>
 <p><strong>Note:</strong></p>
 <p>The Apache Directory Studio plugins require Eclipse 4.2 (Juno) or newer and Java 7 or newer.</p>

Modified: websites/staging/directory/trunk/content/studio/internationalization.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/internationalization.html (original)
+++ websites/staging/directory/trunk/content/studio/internationalization.html Sun Jul  5 22:34:35 2015
@@ -151,9 +151,20 @@
 
 
 
-<h1 id="internationalization-i18n">Internationalization (i18n)</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="internationalization-i18n">Internationalization (i18n)<a class="headerlink" href="#internationalization-i18n" title="Permanent link">&para;</a></h1>
 <p>It exists a good guide on internationalization (and externalizing string) at <a href="http://www.eclipse.org/articles/Article-Internationalization/how2I18n.html">How to Internationalize your Eclipse Plug-In</a>.</p>
-<h2 id="translating-the-current-code">Translating the current code</h2>
+<h2 id="translating-the-current-code">Translating the current code<a class="headerlink" href="#translating-the-current-code" title="Permanent link">&para;</a></h2>
 <p>Translating Studio is not an simple task. There are many files to translate :</p>
 <ul>
 <li>messages.properties</li>
@@ -161,14 +172,12 @@
 <li>help files</li>
 <li>some other semi-random files ;)</li>
 </ul>
-<h2 id="when-writing-code">When writing code...</h2>
+<h2 id="when-writing-code">When writing code...<a class="headerlink" href="#when-writing-code" title="Permanent link">&para;</a></h2>
 <p>When doing the translation for a specific language please add in any case the messages_{language}.properties file of the language to the resource folder, even if it's empty (meaning all translations are taken from the messages.properties file). This will show to other developers, that you've thought about translation but no one was needed.</p>
 <p>Notes:</p>
 <ul>
 <li>The message".properties files are located in the src/main/java/*<em> folder (not following maven's philosophy) to be able to use Eclipse' 'Externalize Strings' wizard also later on. Following maven philosophy (</em>.properties in src/main/resources) the wizard doesn't finds the created properties files anymore.</li>
-<li>
-<p>To replace placeholders we use Eclipse's NLS.bind function, e.g.</p>
-<div class="codehilite"><pre><span class="n">From</span> <span class="n">messages</span><span class="p">.</span><span class="k">properties</span><span class="p">:</span>
+<li>To replace placeholders we use Eclipse's NLS.bind function, e.g.<div class="codehilite"><pre><span class="n">From</span> <span class="n">messages</span><span class="p">.</span><span class="k">properties</span><span class="p">:</span>
 <span class="n">EditAliasesDialog</span><span class="p">.</span><span class="n">TheAliasBegin</span><span class="p">=</span><span class="n">The</span> <span class="n">alias</span> &quot;<span class="p">{</span>0<span class="p">}</span>&quot; <span class="n">is</span> <span class="n">invalid</span><span class="p">.</span>
 
 <span class="n">Will</span> <span class="n">look</span> <span class="n">like</span> <span class="n">in</span> <span class="n">Java</span> <span class="n">code</span><span class="p">:</span>

Modified: websites/staging/directory/trunk/content/studio/news.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/news.html (original)
+++ websites/staging/directory/trunk/content/studio/news.html Sun Jul  5 22:34:35 2015
@@ -151,7 +151,18 @@
 
 
 
-<h1 id="news">News</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="news">News<a class="headerlink" href="#news" title="Permanent link">&para;</a></h1>
 <h2 class="news">Apache Directory Studio 2.0-0-M9 released <em>posted on June 11th, 2015</em></h2>
 
 <p>The Apache Directory Team is pleased to announce the release of Apache Directory Studio 2.0.0-M9, the ninth milestone release of the version 2.0 of its Eclipse based LDAP Browser and Directory client.</p>

Modified: websites/staging/directory/trunk/content/studio/screenshots.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/screenshots.html (original)
+++ websites/staging/directory/trunk/content/studio/screenshots.html Sun Jul  5 22:34:35 2015
@@ -151,7 +151,18 @@
 
 
 
-<h1 id="screenshots">Screenshots</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="screenshots">Screenshots<a class="headerlink" href="#screenshots" title="Permanent link">&para;</a></h1>
 <script src="static/js/FancyZoom.js" type="text/javascript"></script>
 
 <script src="static/js/FancyZoomHTML.js" type="text/javascript"></script>
@@ -186,7 +197,7 @@
     }
 </style>
 
-<h2 id="apache-directory-studio-application">Apache Directory Studio Application</h2>
+<h2 id="apache-directory-studio-application">Apache Directory Studio Application<a class="headerlink" href="#apache-directory-studio-application" title="Permanent link">&para;</a></h2>
 <p><center>
     <table class="screenshot_table" cellpadding="0" cellspacing="0">
         <tr>
@@ -211,7 +222,7 @@
         </tr>
     </table>
 </center></p>
-<h2 id="ldap-browser">LDAP Browser</h2>
+<h2 id="ldap-browser">LDAP Browser<a class="headerlink" href="#ldap-browser" title="Permanent link">&para;</a></h2>
 <p>TODO...</p>
 <p><center>
     <table class="screenshot_table" cellpadding="0" cellspacing="0">
@@ -227,9 +238,9 @@
         </tr>
     </table>
 </center></p>
-<h2 id="ldif-editor">LDIF Editor</h2>
+<h2 id="ldif-editor">LDIF Editor<a class="headerlink" href="#ldif-editor" title="Permanent link">&para;</a></h2>
 <p>TODO...</p>
-<h2 id="schema-editor">Schema Editor</h2>
+<h2 id="schema-editor">Schema Editor<a class="headerlink" href="#schema-editor" title="Permanent link">&para;</a></h2>
 <p>TODO...</p>
 <p><center>
     <table class="screenshot_table" cellpadding="0" cellspacing="0">
@@ -275,9 +286,9 @@
         </tr>
     </table>
 </center></p>
-<h2 id="embedded-apacheds">Embedded ApacheDS</h2>
+<h2 id="embedded-apacheds">Embedded ApacheDS<a class="headerlink" href="#embedded-apacheds" title="Permanent link">&para;</a></h2>
 <p>TODO...</p>
-<h2 id="apacheds-configuration">ApacheDS Configuration</h2>
+<h2 id="apacheds-configuration">ApacheDS Configuration<a class="headerlink" href="#apacheds-configuration" title="Permanent link">&para;</a></h2>
 <p>TODO...</p>
 <p><center>
     <table class="screenshot_table" cellpadding="0" cellspacing="0">
@@ -311,7 +322,7 @@
         </tr>
     </table>
 </center></p>
-<h2 id="aci-editor">ACI Editor</h2>
+<h2 id="aci-editor">ACI Editor<a class="headerlink" href="#aci-editor" title="Permanent link">&para;</a></h2>
 <p><center>
     <table class="screenshot_table" cellpadding="0" cellspacing="0">
         <tr>

Modified: websites/staging/directory/trunk/content/studio/source-repository.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/source-repository.html (original)
+++ websites/staging/directory/trunk/content/studio/source-repository.html Sun Jul  5 22:34:35 2015
@@ -151,27 +151,38 @@
 
 
 
-<h1 id="source-repository">Source Repository</h1>
-<h2 id="source-repository-address">Source Repository Address</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="source-repository">Source Repository<a class="headerlink" href="#source-repository" title="Permanent link">&para;</a></h1>
+<h2 id="source-repository-address">Source Repository Address<a class="headerlink" href="#source-repository-address" title="Permanent link">&para;</a></h2>
 <p>To get the source, you will need to have subversion installed. Just type the following command to get the latest development version:</p>
 <div class="codehilite"><pre><span class="n">svn</span> <span class="n">co</span> <span class="n">http</span><span class="p">:</span><span class="o">//</span><span class="n">svn</span><span class="p">.</span><span class="n">apache</span><span class="p">.</span><span class="n">org</span><span class="o">/</span><span class="n">repos</span><span class="o">/</span><span class="n">asf</span><span class="o">/</span><span class="n">directory</span><span class="o">/</span><span class="n">studio</span><span class="o">/</span><span class="n">trunk</span> <span class="n">studio</span>
 </pre></div>
 
 
 <p>If you are an authorized developer, just check out the code using <em>https</em> instead of <em>http</em>.</p>
-<h2 id="browse-the-sources">Browse the Sources</h2>
+<h2 id="browse-the-sources">Browse the Sources<a class="headerlink" href="#browse-the-sources" title="Permanent link">&para;</a></h2>
 <p>You can view and explore online SVN at this address:</p>
 <blockquote>
 <p><a href="http://svn.apache.org/viewvc/directory/studio/trunk/">http://svn.apache.org/viewvc/directory/studio/trunk/</a></p>
 </blockquote>
-<h2 id="git-mirrors">Git Mirrors</h2>
+<h2 id="git-mirrors">Git Mirrors<a class="headerlink" href="#git-mirrors" title="Permanent link">&para;</a></h2>
 <p>There is a read-only Git mirror available: </p>
 <ul>
 <li>Git protocol: <code>git://git.apache.org/directory-studio.git</code></li>
 <li>HTTP protocol: <code>http://git.apache.org/directory-studio.git</code></li>
 </ul>
 <p>The git repository is also mirrored to Github: <a href="https://github.com/apache/directory-studio/">https://github.com/apache/directory-studio/</a>.</p>
-<h2 id="source-repository-organization">Source Repository Organization</h2>
+<h2 id="source-repository-organization">Source Repository Organization<a class="headerlink" href="#source-repository-organization" title="Permanent link">&para;</a></h2>
 <p>The repository is organized as follows :</p>
 <div class="codehilite"><pre><span class="o">|--</span> <span class="n">pom</span><span class="o">-</span><span class="n">first</span><span class="p">.</span><span class="n">xml</span>                                 <span class="n">pom</span><span class="p">.</span><span class="n">xml</span> <span class="n">to</span> <span class="n">generate</span> <span class="n">the</span> <span class="n">Eclipse</span> <span class="n">Target</span> <span class="n">Platform</span> <span class="n">and</span> <span class="n">the</span> <span class="n">MANIFEST</span><span class="p">.</span><span class="n">MF</span> <span class="n">files</span>
 <span class="o">|--</span> <span class="n">pom</span><span class="p">.</span><span class="n">xml</span>                                       <span class="n">The</span> <span class="n">main</span> <span class="n">pom</span>

Modified: websites/staging/directory/trunk/content/studio/testimonials.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/testimonials.html (original)
+++ websites/staging/directory/trunk/content/studio/testimonials.html Sun Jul  5 22:34:35 2015
@@ -151,9 +151,20 @@
 
 
 
-<h1 id="testimonials">Testimonials</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="testimonials">Testimonials<a class="headerlink" href="#testimonials" title="Permanent link">&para;</a></h1>
 <p>This page is dedicated to people using <em>{<em>}Apache Directory Studio{</em>}</em> and like it !</p>
-<h3 id="in-english">In English:</h3>
+<h3 id="in-english">In English:<a class="headerlink" href="#in-english" title="Permanent link">&para;</a></h3>
 <ul>
 <li><a href="http://www.eclipseplugincentral.com/Web_Links-index-req-viewlink-cid-896.html">http://www.eclipseplugincentral.com/Web_Links-index-req-viewlink-cid-896.html</a></li>
 <li><a href="http://www.eclipse-plugins.info/eclipse/plugin_details.jsp?id=1752">http://www.eclipse-plugins.info/eclipse/plugin_details.jsp?id=1752</a></li>
@@ -165,24 +176,24 @@
 <li><a href="http://marksparhawk.com/articles/2007/10/03/apache-does-ldap-well">http://marksparhawk.com/articles/2007/10/03/apache-does-ldap-well</a></li>
 <li><a href="http://www.mikeperham.com/2007/09/28/using-apache-ds-part-2/">http://www.mikeperham.com/2007/09/28/using-apache-ds-part-2/</a></li>
 </ul>
-<h3 id="in-french">In French:</h3>
+<h3 id="in-french">In French:<a class="headerlink" href="#in-french" title="Permanent link">&para;</a></h3>
 <ul>
 <li><a href="http://anothergeekwebsite.com/fr/2007/03/ldapstudio">http://anothergeekwebsite.com/fr/2007/03/ldapstudio</a></li>
 </ul>
-<h3 id="in-hungarian">In Hungarian:</h3>
+<h3 id="in-hungarian">In Hungarian:<a class="headerlink" href="#in-hungarian" title="Permanent link">&para;</a></h3>
 <ul>
 <li><a href="http://www.kroy.hu/blog/?p=34#comment-12">http://www.kroy.hu/blog/?p=34#comment-12</a></li>
 </ul>
-<h3 id="in-czech">In Czech:</h3>
+<h3 id="in-czech">In Czech:<a class="headerlink" href="#in-czech" title="Permanent link">&para;</a></h3>
 <ul>
 <li><a href="http://www.benak.net/node/33">http://www.benak.net/node/33</a></li>
 </ul>
-<h3 id="in-german">In German:</h3>
+<h3 id="in-german">In German:<a class="headerlink" href="#in-german" title="Permanent link">&para;</a></h3>
 <ul>
 <li><a href="http://blog.dogan.ch/2007/09/28/apache-directory-studio/">http://blog.dogan.ch/2007/09/28/apache-directory-studio/</a></li>
 <li><a href="http://www.hare.at/ccldap/index.html">http://www.hare.at/ccldap/index.html</a></li>
 </ul>
-<h3 id="george-stoianov-says">George Stoianov says:</h3>
+<h3 id="george-stoianov-says">George Stoianov says:<a class="headerlink" href="#george-stoianov-says" title="Permanent link">&para;</a></h3>
 <blockquote>
 <p>I have spend only a limited time with LDAP Studio maybe 1-2 hours, so
 far and I am really impressed with the way it works and behaves. I

Modified: websites/staging/directory/trunk/content/studio/update/index.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/update/index.html (original)
+++ websites/staging/directory/trunk/content/studio/update/index.html Sun Jul  5 22:34:35 2015
@@ -151,7 +151,18 @@
 
 
 
-<h2 id="update-site">Update Site</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="update-site">Update Site<a class="headerlink" href="#update-site" title="Permanent link">&para;</a></h2>
 <p>This is the update site for Apache Directory Studio. Please visit <a href="../installation-in-eclipse.html">Installing Apache Directory Studio in Eclipse</a> for instructions how to use it.</p>
 
 

Modified: websites/staging/directory/trunk/content/studio/update/product/index.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/update/product/index.html (original)
+++ websites/staging/directory/trunk/content/studio/update/product/index.html Sun Jul  5 22:34:35 2015
@@ -151,7 +151,18 @@
 
 
 
-<h2 id="update-site">Update Site</h2>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h2 id="update-site">Update Site<a class="headerlink" href="#update-site" title="Permanent link">&para;</a></h2>
 <p>This is the update site for Apache Directory Studio. Please visit <a href="../../installation-in-eclipse.html">Installing Apache Directory Studio in Eclipse</a> for instructions how to use it.</p>
 
 

Modified: websites/staging/directory/trunk/content/studio/users-guide.html
==============================================================================
--- websites/staging/directory/trunk/content/studio/users-guide.html (original)
+++ websites/staging/directory/trunk/content/studio/users-guide.html Sun Jul  5 22:34:35 2015
@@ -151,24 +151,35 @@
 
 
 
-<h1 id="users-guide">User's Guide</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="users-guide">User's Guide<a class="headerlink" href="#users-guide" title="Permanent link">&para;</a></h1>
 <p>Here are the User's Guides available for Apache Directory Studio:</p>
-<h2 id="ldap-browser">LDAP Browser</h2>
+<h2 id="ldap-browser">LDAP Browser<a class="headerlink" href="#ldap-browser" title="Permanent link">&para;</a></h2>
 <p><img alt="HTML Guide" src="users-guide.data/html.png" /> <a href="users-guide/ldap_browser/">Click here to consult the LDAP Browser User's Guide</a></p>
 <p><img alt="PDF Guide" src="users-guide.data/pdf.png" /> <a href="users-guide/Apache_Directory_Studio_LDAP_Browser_User_Guide.pdf">The LDAP Browser User's Guide is also available as PDF </a></p>
-<h2 id="ldif-editor">LDIF Editor</h2>
+<h2 id="ldif-editor">LDIF Editor<a class="headerlink" href="#ldif-editor" title="Permanent link">&para;</a></h2>
 <p><img alt="HTML Guide" src="users-guide.data/html.png" /> <a href="users-guide/ldif_editor/">Click here to consult the LDIF Editor User's Guide</a></p>
 <p><img alt="PDF Guide" src="users-guide.data/pdf.png" /> <a href="users-guide/Apache_Directory_Studio_LDIF_Editor_User_Guide.pdf">The LDIF Editor User's Guide is also available as PDF </a></p>
-<h2 id="schema-editor">Schema Editor</h2>
+<h2 id="schema-editor">Schema Editor<a class="headerlink" href="#schema-editor" title="Permanent link">&para;</a></h2>
 <p><img alt="HTML Guide" src="users-guide.data/html.png" /> <a href="users-guide/schema_editor/">Click here to consult the Schema Editor User's Guide</a></p>
 <p><img alt="PDF Guide" src="users-guide.data/pdf.png" /> <a href="users-guide/Apache_Directory_Studio_Schema_Editor_User_Guide.pdf">The Schema Editor User's Guide is also available as PDF </a></p>
-<h2 id="apache-directory-server">Apache Directory Server</h2>
+<h2 id="apache-directory-server">Apache Directory Server<a class="headerlink" href="#apache-directory-server" title="Permanent link">&para;</a></h2>
 <p><img alt="HTML Guide" src="users-guide.data/html.png" /> <a href="users-guide/apacheds/">Click here to consult the Apache Directory Server User's Guide</a></p>
 <p><img alt="PDF Guide" src="users-guide.data/pdf.png" /> <a href="users-guide/Apache_Directory_Studio_Apache_DS_User_Guide.pdf">The Apache Directory Server User's Guide is also available as PDF </a></p>
-<h2 id="apache-directory-server-configuration">Apache Directory Server Configuration</h2>
+<h2 id="apache-directory-server-configuration">Apache Directory Server Configuration<a class="headerlink" href="#apache-directory-server-configuration" title="Permanent link">&para;</a></h2>
 <p><img alt="HTML Guide" src="users-guide.data/html.png" /> <a href="users-guide/apacheds_configuration/">Click here to consult the Apache Directory Server Configuration User's Guide</a></p>
 <p><img alt="PDF Guide" src="users-guide.data/pdf.png" /> <a href="users-guide/Apache_Directory_Studio_Apache_DS_Configuration_User_Guide.pdf">The Apache Directory Server Configuration User's Guide is also available as PDF </a></p>
-<h2 id="apache-directory-studio">Apache Directory Studio</h2>
+<h2 id="apache-directory-studio">Apache Directory Studio<a class="headerlink" href="#apache-directory-studio" title="Permanent link">&para;</a></h2>
 <p><img alt="HTML Guide" src="users-guide.data/html.png" /> <a href="users-guide/apache_directory_studio/">Click here to consult the Apache Directory Studio User's Guide</a></p>
 <p><img alt="PDF Guide" src="users-guide.data/pdf.png" /> <a href="users-guide/Apache_Directory_Studio_User_Guide.pdf">The User's Guide is also available as PDF </a></p>
 

Modified: websites/staging/directory/trunk/content/team.html
==============================================================================
--- websites/staging/directory/trunk/content/team.html (original)
+++ websites/staging/directory/trunk/content/team.html Sun Jul  5 22:34:35 2015
@@ -101,7 +101,7 @@
     <ul>
         <li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./studio/downloads.html">Studio 2.0.0-M9</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
-        <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+        <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
         <!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,7 +162,18 @@
 
 
 
-<h1 id="the-apache-directory-project-committee">The Apache Directory Project Committee</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="the-apache-directory-project-committee">The Apache Directory Project Committee<a class="headerlink" href="#the-apache-directory-project-committee" title="Permanent link">&para;</a></h1>
 <table>
 <thead>
 <tr>
@@ -267,7 +278,7 @@
 </tr>
 </tbody>
 </table>
-<h1 id="the-apache-directory-project-committers">The Apache Directory Project Committers</h1>
+<h1 id="the-apache-directory-project-committers">The Apache Directory Project Committers<a class="headerlink" href="#the-apache-directory-project-committers" title="Permanent link">&para;</a></h1>
 <table>
 <thead>
 <tr>
@@ -373,7 +384,7 @@
 </tbody>
 </table>
 <p>To be continued ...</p>
-<h1 id="emeritus-committers-and-pmcs">Emeritus committers and PMCs</h1>
+<h1 id="emeritus-committers-and-pmcs">Emeritus committers and PMCs<a class="headerlink" href="#emeritus-committers-and-pmcs" title="Permanent link">&para;</a></h1>
 <table>
 <thead>
 <tr>

Modified: websites/staging/directory/trunk/content/testimonies.html
==============================================================================
--- websites/staging/directory/trunk/content/testimonies.html (original)
+++ websites/staging/directory/trunk/content/testimonies.html Sun Jul  5 22:34:35 2015
@@ -101,7 +101,7 @@
     <ul>
         <li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./studio/downloads.html">Studio 2.0.0-M9</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
-        <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+        <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
         <!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,7 +162,18 @@
 
 
 
-<h1 id="testimonials">Testimonials</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="testimonials">Testimonials<a class="headerlink" href="#testimonials" title="Permanent link">&para;</a></h1>
 <p>This page collects testimonies from Apache Directory Server users, and expose what they are using it for.</p>
 <ul>
 <li>The openthinclient.org project uses ADS as an embedded directory server to store all kinds of configuration data.

Modified: websites/staging/directory/trunk/content/vision.html
==============================================================================
--- websites/staging/directory/trunk/content/vision.html (original)
+++ websites/staging/directory/trunk/content/vision.html Sun Jul  5 22:34:35 2015
@@ -101,7 +101,7 @@
     <ul>
         <li><a href="./apacheds/downloads.html">ApacheDS 2.0.0-M20</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./studio/downloads.html">Studio 2.0.0-M9</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
-        <li><a href="./api/downloads.html">LDAP API 1.0.0-M30</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
+        <li><a href="./api/downloads.html">LDAP API 1.0.0-M31</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./mavibot/downloads.html">Mavibot 1.0.0-M7</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li>
         <li><a href="./fortress/downloads.html">Fortress 1.0-RC40</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li-->
         <!-- <li><a href="./escimo/downloads.html">eSCIMo 1.0.0-M1</a>&nbsp;&nbsp;<IMG src="./images/new_badge.gif" alt="" style="margin-bottom:-3px;" border="0"></li> -->
@@ -162,7 +162,18 @@
 
 
 
-<h1 id="architecting-the-modern-ldap-renaissance-the-apache-directory-vision">Architecting the Modern LDAP Renaissance: The Apache Directory Vision</h1>
+<style type="text/css">
+/* The following code is added by mdx_elementid.py
+   It was originally lifted from http://subversion.apache.org/style/site.css */
+/*
+ * Hide class="elementid-permalink", except when an enclosing heading
+ * has the :hover property.
+ */
+.headerlink, .elementid-permalink {
+  visibility: hidden;
+}
+h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style>
+<h1 id="architecting-the-modern-ldap-renaissance-the-apache-directory-vision">Architecting the Modern LDAP Renaissance: The Apache Directory Vision<a class="headerlink" href="#architecting-the-modern-ldap-renaissance-the-apache-directory-vision" title="Permanent link">&para;</a></h1>
 <p>by Alex Karasulu, Founder of the <a href="http://directory.apache.org">Apache Directory Project</a>, October 2002
 This paper was later, in September 2007, submitted to and accepted by the <a href="http://www.guug.de/veranstaltungen/ldapcon2007/">1st International Conference on LDAP</a>, Cologne (Germany)</p>
 <div class="toc">
@@ -178,7 +189,7 @@ This paper was later, in September 2007,
 </li>
 </ul>
 </div>
-<h2 id="abstract">Abstract</h2>
+<h2 id="abstract">Abstract<a class="headerlink" href="#abstract" title="Permanent link">&para;</a></h2>
 <div class="codehilite"><pre><span class="n">Directory</span> <span class="n">technology</span> <span class="n">is</span> <span class="n">an</span> <span class="n">indivisible</span> <span class="n">cornerstone</span> <span class="n">in</span> <span class="n">computing</span> <span class="n">science</span> <span class="n">and</span> <span class="n">LDAP</span> <span class="n">specifically</span> <span class="n">is</span> <span class="n">essential</span> <span class="n">in</span> 
 <span class="n">several</span> <span class="n">industries</span> <span class="n">however</span> <span class="n">it</span> <span class="n">is</span> <span class="n">severely</span> <span class="n">underutilized</span><span class="p">.</span>
 
@@ -204,7 +215,7 @@ This paper was later, in September 2007,
 </pre></div>
 
 
-<h2 id="drivers-leading-to-the-birth-of-the-directory">Drivers Leading to the Birth of the Directory</h2>
+<h2 id="drivers-leading-to-the-birth-of-the-directory">Drivers Leading to the Birth of the Directory<a class="headerlink" href="#drivers-leading-to-the-birth-of-the-directory" title="Permanent link">&para;</a></h2>
 <p>Several systems slowly appeared in the arsenal of tools used daily by those within and across organizations. Data architects quickly could characterized two logical categories of information spanning across all domains:</p>
 <ul>
 <li>Static information shared across applications and systems read frequently yet seldom altered.</li>
@@ -221,22 +232,22 @@ This paper was later, in September 2007,
 <p>The telecommunication industry in Europe, in particular, felt this burden while managing shared information, specifically subscriber directories. Telephone companies in Europe, some national providers and other international providers, managed profiles for subscribers, a subset of which, needed to be published for public access.</p>
 <p>The ITU responded with the X.500 series of specifications. The Directory specifications addressed these specific concerns for accessing information shared across organizations, located in separate stores and managed by several different authorities. The access model and authoritative model enabled organizations to publish subscriber information and allow others to access it while delegating the management of access control, schema and other aspects to the proper authorities. As a standard it was way ahead of its time.</p>
 <p>The X.500 specifications reveal a unique data access and authoritative model designed specifically for the category of static shared data we defined above. It is a cornerstone technology as is the relational database for the second category.</p>
-<h2 id="demand-for-directories-should-be-high">Demand for Directories Should Be High</h2>
+<h2 id="demand-for-directories-should-be-high">Demand for Directories Should Be High<a class="headerlink" href="#demand-for-directories-should-be-high" title="Permanent link">&para;</a></h2>
 <p>Directories expose a unique model for efficiently accessing relatively static information shared across multiple systems. Directory protocol designers intended the protocol to address a class of specific problems through a standard means to access shared information centrally while providing high availability. Existing storage paradigms failed to solve these problems due to inherent limitations in their design.</p>
 <p>These data management problems fall under the domain of data integration. To integrate systems one must integrate both the data and the processes. Interoperating systems often need to access the same information however many systems simply duplicate that information (in relational databases) rather than accessing it from a centralized service (the directory). As a result multiple copies of the same information exist across these systems. Data synchronization technologies emerged to address these issues of duplication such as meta-directories (not real directories). These technologies never really solved all the issues of data duplication: they merely facilitated the export, transformation and import of data across systems. The serious issue of determining the authoritative copy still remained.</p>
 <p>For some time, commercial entities avoided addressing these integration problems by centralizing access to this shared information. The market fueled the push of OLTP systems since the transaction equated to money. As markets became saturated as several competitors appeared, businesses started focusing on gains through efficiency. To streamline development and maintenance better integration was needed while allowing transactions to span across interoperating systems. This increased the need for directories.</p>
 <p>Aspects of growth naturally contribute to the demand for Directory technologies. As the number of users, organizations, systems, services and machines expand the problems of integration only increase without applying the correct remedy. In fact, the vast majority of today's problems are primary integration problems. Hence one would expect the utilization of Directories to increase proportionally with the increased demand. Unfortunately, a proportional increase in demand for Directories has not been observed.</p>
-<h2 id="barriers-of-adoption">Barriers of Adoption</h2>
+<h2 id="barriers-of-adoption">Barriers of Adoption<a class="headerlink" href="#barriers-of-adoption" title="Permanent link">&para;</a></h2>
 <p>Although Directories, namely LDAP Directories, have proliferated over the past two decades, their adoption has not been commensurate with the demand one would expect. Several factors may be attributed to this less than optimal adoption rate.</p>
 <p>Directories still feel alien to most developers. Many admit, in theory, to a directory as the ideal access model for shared information in their applications however most fall back to using a relational database instead. Why?</p>
 <p>First there is no formal education around directory technologies while several courses around relational database systems exist. This might explain in part why developers are much more comfortable with keeping their Directory information stored and accessed from an RDBMS. As a result, finding qualified Directory experts is difficult. Every generalist knows how to use an RDBMS, yet costly specialists are needed to design, operate and maintain directories. The cost and availability of specialized engineers factor into design decisions especially if the process is formally conducted.</p>
 <p>Developers may also fall back to using an RDBMS instead of a Directory because of a lack of rich integration tier constructs (like triggers, views and stored procedures). These very useful constructs are missing in Directories yet have been available in relational databases for decades. Today's heavy integration needs demand these constructs. For example the demand for the event driven provisioning of information could be elegantly solved using triggers and stored procedures as entries are added, updated and deleted. Data architects and developers in this respect have been left in the dark-ages with LDAP while the RDBMS has given them what they wanted/needed at the price of compounding their problems with data duplication.</p>
 <p>Perhaps the most significant factor driving these faulty decisions is the lack of LDAP tooling. There are myriads of RDBMS tools for various aspects: tuning, accessing, and designing. Tools for the RDBMS appeared with a vengeance to enable designers to rapidly prototype new OLTP systems and thus bring them to market faster. Less confident generalists could even design databases and manipulate them thanks to these tools which abstracted away the details to just get the job done. The tools made engineers and non-engineers productive in building database driven applications rapidly. Unfortunately, there barely are any good browsers for LDAP much less topology/schema, design and tuning tools. The barren tooling landscape leaves developers and data architects exposed enough to turn back to the RDBMS for immediate comfort. This temporary gain is at the cost of long term data bottle necks or synchronization issues.</p>
 <p>Regardless of which factor prevents most the uptake of LDAP, the fact remains: the wrong decisions are being made more often than the right ones. It's a matter of time before Directories are considered antiquated technologies unless they can accommodate modern needs. Directories must be compelling enough for data architects and developers to decide to utilize them for their strengths in theory and in practice.</p>
-<h2 id="renovating-ldap-directories-for-the-21st-century">Renovating (LDAP) Directories for the 21st Century</h2>
+<h2 id="renovating-ldap-directories-for-the-21st-century">Renovating (LDAP) Directories for the 21st Century<a class="headerlink" href="#renovating-ldap-directories-for-the-21st-century" title="Permanent link">&para;</a></h2>
 <p>Several factors are not under the immediate control of the LDAP community however enough are to bring LDAP to the 21st century. First and foremost, LDAP tooling must improve. We need tools to model LDAP directories properly for topology and schema. Designers should be guided on how they can properly use more of the esoteric constructs to control the naming, and hierarchy of the directory. There's more to directory design than just objectClasses and attributeTypes.</p>
 <p>Secondly the protocol must expand LDAP to include standard mechanisms for declaring triggers, stored procedures and views. These two aspects alone contribute to the vast majority of reasons why relational databases store information best accessed from a directory. Allowing these new constructs for a directory will enable virtualization, provisioning, referential integrity, and server interaction with the external environment. Rather than only exposing access to static information (white pages) the directory could be utilized to solve many more problems confronting designers and developers in today's integration era. The Directory would truly become the Swiss Army Knife(TM) of integration tools in the data architect's tool chest.</p>
-<h2 id="conclusion-the-aim-of-the-apache-directory-project">Conclusion: The Aim of the Apache Directory Project</h2>
+<h2 id="conclusion-the-aim-of-the-apache-directory-project">Conclusion: The Aim of the Apache Directory Project<a class="headerlink" href="#conclusion-the-aim-of-the-apache-directory-project" title="Permanent link">&para;</a></h2>
 <p>At the Apache Directory Project, there are two LDAP specific projects. The first is a pure Java LDAP Server called Apache Directory Server (ApacheDS) which has been written and certified by the Open Group for LDAPv3. It was started in reaction to the often brittle code that was too hard to manage: the code was written in C and had preprocessor directives strewn all over it for porting.</p>
 <p>The other LDAP related project is called Apache Directory Studio. It is intended to provide the missing LDAP tooling support in addition to Apache Directory Server specific management utilities.</p>
 <p>The general motives for forming the Apache Directory Project can be summarized with the points below:</p>



Mime
View raw message