You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by bu...@apache.org on 2015/07/06 00:34:38 UTC
svn commit: r957126 [1/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/ fortress...
Author: buildbot
Date: Sun Jul 5 22:34:35 2015
New Revision: 957126
Log:
Staging update by buildbot for directory
Modified:
websites/staging/directory/trunk/content/ (props changed)
websites/staging/directory/trunk/content/apacheds/advanced-ug/0-community.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/0.1-reporting-bugs.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/0.2-building-trunks.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/0.3-contributing.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/1-architecture.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/1.1-architecture-overview.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/1.2-network.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/1.3-directory-service.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/1.5-backend.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/2.1-config-description.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2-instance-layout.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.1-debian-instance-layout.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.2-rpm-instance-layout.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.3-macosx-instance-layout.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.4-windows-instance-layout.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.5-generic-instance-layout.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/3-admin-model.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/3.1-administrative-points.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/3.2-operations-on-an-administrativepoint.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4-authentication-and-authorization.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1-authentication.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.1-simple-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.1.1-anonymous-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.1.2-name-password-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.1.3-unauthenticated-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2-sasl-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.1-sasl-plain-text-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.2-sasl-cram-md5-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.3-sasl-digest-md5-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.4-sasl-gssapi-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.5-sasl-external-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.2.6-sasl-ntlm-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.3-kerberos-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.1.4-certificate-authn.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2-authorization.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.1-introduction.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.10-aci-grammar.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.11-links-and-references.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.2-definitions.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.3-enabling-access-control.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4-aci-types.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.1-entryaci.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.2-prescriptiveaci.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.4.3-subentryaci.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5-aci-elements.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.1-userclasses.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.2-protecteditems.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.3-permissions.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.5.4-subtrees.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6-the-acdf-engine.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.1-how-it-works.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.2-selections.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.3-constraints.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.6.4-priority.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7-using-acis-trail.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7.1-enable-authenticated-users-to-browse-and-read-entries.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.7.2-allow-self-password-modify.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.8-acis-administration.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.2.9-migration-from-other-ldap-servers.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/4.3-password-policy.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/5-administration.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/5.1-layout.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/5.2-start-stop.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/5.3-logs.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/5.4-replication.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/6-implementing-interceptor.html
websites/staging/directory/trunk/content/apacheds/advanced-ug/7-embedding-apacheds.html
websites/staging/directory/trunk/content/apacheds/advanced-user-guide.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1-how-to-begin.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.1-what-apacheds-is.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.2-some-background.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.3-installing-and-starting.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.4-basic-configuration-tasks.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.1-changing-server-port.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.2-changing-admin-password.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.3-adding-partition.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.4-configure-logging.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.4.5-anonymous-access.html
websites/staging/directory/trunk/content/apacheds/basic-ug/1.5-sample-configuration.html
websites/staging/directory/trunk/content/apacheds/basic-ug/2-handling-data.html
websites/staging/directory/trunk/content/apacheds/basic-ug/2.1-data-modification.html
websites/staging/directory/trunk/content/apacheds/basic-ug/2.1.1-adding-entries.html
websites/staging/directory/trunk/content/apacheds/basic-ug/2.1.2-deleting-entries.html
websites/staging/directory/trunk/content/apacheds/basic-ug/2.2-searching-data.html
websites/staging/directory/trunk/content/apacheds/basic-ug/2.2.1-simple-search.html
websites/staging/directory/trunk/content/apacheds/basic-ug/2.2.2-more-search-options.html
websites/staging/directory/trunk/content/apacheds/basic-ug/2.3-introducing-schema.html
websites/staging/directory/trunk/content/apacheds/basic-ug/2.3.1-adding-schema-elements.html
websites/staging/directory/trunk/content/apacheds/basic-ug/3-basic-security.html
websites/staging/directory/trunk/content/apacheds/basic-ug/3.1-authentication-options.html
websites/staging/directory/trunk/content/apacheds/basic-ug/3.2-basic-authorization.html
websites/staging/directory/trunk/content/apacheds/basic-ug/3.3-enabling-ssl.html
websites/staging/directory/trunk/content/apacheds/basic-ug/4-integrating-apacheds.html
websites/staging/directory/trunk/content/apacheds/basic-ug/4.1-mozilla-thunderbird.html
websites/staging/directory/trunk/content/apacheds/basic-user-guide.html
websites/staging/directory/trunk/content/apacheds/coding-standards.html
websites/staging/directory/trunk/content/apacheds/configuration/ads-2.0-configuration.html
websites/staging/directory/trunk/content/apacheds/configuration/adsconfig.html
websites/staging/directory/trunk/content/apacheds/developer-guide.html
websites/staging/directory/trunk/content/apacheds/download-old-versions.html
websites/staging/directory/trunk/content/apacheds/downloads.html
websites/staging/directory/trunk/content/apacheds/features.html
websites/staging/directory/trunk/content/apacheds/index.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1-kerberos.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.1-introduction.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.1.1-realms.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.1.2-principals.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.1.3-keys.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.1.4-kdc.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.1.5-database.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.1.6-as.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.1.7-tgs.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.1.8-tickets.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.2-resources.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.2.1-kerberos-articles.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.2.2-microsoft-compatibility.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/1.2.3-standards.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/2-kerberos-config.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/2.1-installing.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/2.2-ldap-server-config.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/2.3-kerberos-server-config.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/2.4-kerberos-ulp.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/2.5-pkinit.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/2.6-cross-realm.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/3-kerberos-admin.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/3.1-start-stop.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/3.2-managing-clients-services.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/3.3-change-password.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/3.4-logs.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/3.5-replication.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/3.6-backup-restore.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/4-using-kerberos.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/4.1-authenticate-kinit.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/4.2-authenticate-studio.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/5-interoperability.html
websites/staging/directory/trunk/content/apacheds/kerberos-ug/6-glossary.html
websites/staging/directory/trunk/content/apacheds/kerberos-user-guide.html
websites/staging/directory/trunk/content/apacheds/news.html
websites/staging/directory/trunk/content/api/coding-standards.html
websites/staging/directory/trunk/content/api/developer-guide.html
websites/staging/directory/trunk/content/api/download-old-versions.html
websites/staging/directory/trunk/content/api/download/download-archive.html
websites/staging/directory/trunk/content/api/download/download-sources.html
websites/staging/directory/trunk/content/api/downloads.html
websites/staging/directory/trunk/content/api/five-minutes-tutorial.html
websites/staging/directory/trunk/content/api/groovy-api/1-groovy-ldap-download.html
websites/staging/directory/trunk/content/api/groovy-api/2-groovy-ldap-user-guide.html
websites/staging/directory/trunk/content/api/groovy-api/3-groovy-ldap-implementation.html
websites/staging/directory/trunk/content/api/groovy-api/4-groovy-ldap-building.html
websites/staging/directory/trunk/content/api/groovy-api/5-groovy-ldap-reference.html
websites/staging/directory/trunk/content/api/groovy-api/6-groovy-ldap-origin.html
websites/staging/directory/trunk/content/api/groovy-ldap.html
websites/staging/directory/trunk/content/api/index.html
websites/staging/directory/trunk/content/api/java-api.html
websites/staging/directory/trunk/content/api/news.html
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/user-guide/1.1-java-and-ldap.html
websites/staging/directory/trunk/content/api/user-guide/1.2-ldap-in-a-few-words.html
websites/staging/directory/trunk/content/api/user-guide/1.3-apache-ldap-api-rational.html
websites/staging/directory/trunk/content/api/user-guide/1.4-preparation-to-code.html
websites/staging/directory/trunk/content/api/user-guide/2-basic-ldap-api-usage.html
websites/staging/directory/trunk/content/api/user-guide/2.1-connection-disconnection.html
websites/staging/directory/trunk/content/api/user-guide/2.10-ldap-connection-template.html
websites/staging/directory/trunk/content/api/user-guide/2.11-filter-builder.html
websites/staging/directory/trunk/content/api/user-guide/2.2-binding-unbinding.html
websites/staging/directory/trunk/content/api/user-guide/2.3-searching.html
websites/staging/directory/trunk/content/api/user-guide/2.4-adding.html
websites/staging/directory/trunk/content/api/user-guide/2.5-deleting.html
websites/staging/directory/trunk/content/api/user-guide/2.6-modifying.html
websites/staging/directory/trunk/content/api/user-guide/2.7-moving-renaming.html
websites/staging/directory/trunk/content/api/user-guide/2.8-comparing.html
websites/staging/directory/trunk/content/api/user-guide/2.9-exception-management.html
websites/staging/directory/trunk/content/api/user-guide/3-advanced-ldap-api-usage.html
websites/staging/directory/trunk/content/api/user-guide/3.1-controls.html
websites/staging/directory/trunk/content/api/user-guide/3.2-extended-operations.html
websites/staging/directory/trunk/content/api/user-guide/3.3-referrals.html
websites/staging/directory/trunk/content/api/user-guide/3.4-aliases.html
websites/staging/directory/trunk/content/api/user-guide/3.5-ldif-dsml.html
websites/staging/directory/trunk/content/api/user-guide/3.6-abandonning.html
websites/staging/directory/trunk/content/api/user-guide/3.7-server-informations.html
websites/staging/directory/trunk/content/api/user-guide/4-schema-management.html
websites/staging/directory/trunk/content/api/user-guide/4.1-schema-manager.html
websites/staging/directory/trunk/content/api/user-guide/4.2-attribute-types.html
websites/staging/directory/trunk/content/api/user-guide/4.3-dit-content-rules.html
websites/staging/directory/trunk/content/api/user-guide/4.4-dit-structure-rules.html
websites/staging/directory/trunk/content/api/user-guide/4.5-matching-rules.html
websites/staging/directory/trunk/content/api/user-guide/4.6-matching-rule-uses.html
websites/staging/directory/trunk/content/api/user-guide/4.7-object-classes.html
websites/staging/directory/trunk/content/api/user-guide/4.8-name-forms.html
websites/staging/directory/trunk/content/api/user-guide/4.9-syntaxes.html
websites/staging/directory/trunk/content/api/user-guide/5-ldap-security.html
websites/staging/directory/trunk/content/api/user-guide/5.1-aci-and-acls.html
websites/staging/directory/trunk/content/api/user-guide/5.2-ssl.html
websites/staging/directory/trunk/content/api/user-guide/5.3-start-tls.html
websites/staging/directory/trunk/content/api/user-guide/6-ldap-data-structures.html
websites/staging/directory/trunk/content/api/user-guide/6.1-administrative-point.html
websites/staging/directory/trunk/content/api/user-guide/6.10-dit-content-rule.html
websites/staging/directory/trunk/content/api/user-guide/6.11-dit-structure-rule.html
websites/staging/directory/trunk/content/api/user-guide/6.12-entry.html
websites/staging/directory/trunk/content/api/user-guide/6.13-expr-node.html
websites/staging/directory/trunk/content/api/user-guide/6.14-ldap-comparator.html
websites/staging/directory/trunk/content/api/user-guide/6.15-ldap-result.html
websites/staging/directory/trunk/content/api/user-guide/6.16-ldap-syntax.html
websites/staging/directory/trunk/content/api/user-guide/6.17-ldap-url.html
websites/staging/directory/trunk/content/api/user-guide/6.18-ldif-control.html
websites/staging/directory/trunk/content/api/user-guide/6.19-ldif-entry.html
websites/staging/directory/trunk/content/api/user-guide/6.2-administrative-role.html
websites/staging/directory/trunk/content/api/user-guide/6.20-matching-rule.html
websites/staging/directory/trunk/content/api/user-guide/6.21-matching-rule-use.html
websites/staging/directory/trunk/content/api/user-guide/6.22-message.html
websites/staging/directory/trunk/content/api/user-guide/6.23-modification.html
websites/staging/directory/trunk/content/api/user-guide/6.24-name-form.html
websites/staging/directory/trunk/content/api/user-guide/6.25-normalizer.html
websites/staging/directory/trunk/content/api/user-guide/6.26-object-class.html
websites/staging/directory/trunk/content/api/user-guide/6.27-oid.html
websites/staging/directory/trunk/content/api/user-guide/6.28-rdn.html
websites/staging/directory/trunk/content/api/user-guide/6.29-referral.html
websites/staging/directory/trunk/content/api/user-guide/6.3-attribute.html
websites/staging/directory/trunk/content/api/user-guide/6.30-refinment.html
websites/staging/directory/trunk/content/api/user-guide/6.31-schema-manager.html
websites/staging/directory/trunk/content/api/user-guide/6.32-subentry.html
websites/staging/directory/trunk/content/api/user-guide/6.33-subtree-specification.html
websites/staging/directory/trunk/content/api/user-guide/6.34-syntax-checker.html
websites/staging/directory/trunk/content/api/user-guide/6.35-value.html
websites/staging/directory/trunk/content/api/user-guide/6.4-attribute-type.html
websites/staging/directory/trunk/content/api/user-guide/6.5-ava.html
websites/staging/directory/trunk/content/api/user-guide/6.6-csn.html
websites/staging/directory/trunk/content/api/user-guide/6.7-control.html
websites/staging/directory/trunk/content/api/user-guide/6.8-cursor.html
websites/staging/directory/trunk/content/api/user-guide/6.9-dn.html
websites/staging/directory/trunk/content/api/user-guide/7-requests-responses.html
websites/staging/directory/trunk/content/api/user-guide/7.1-abandon-request.html
websites/staging/directory/trunk/content/api/user-guide/7.10-extended-request.html
websites/staging/directory/trunk/content/api/user-guide/7.11-extended-response.html
websites/staging/directory/trunk/content/api/user-guide/7.12-intermediate-response.html
websites/staging/directory/trunk/content/api/user-guide/7.13-mod-dn-request.html
websites/staging/directory/trunk/content/api/user-guide/7.14-mod-dn-response.html
websites/staging/directory/trunk/content/api/user-guide/7.15-modify-request.html
websites/staging/directory/trunk/content/api/user-guide/7.16-modify-response.html
websites/staging/directory/trunk/content/api/user-guide/7.17-search-request.html
websites/staging/directory/trunk/content/api/user-guide/7.18-search-result-done.html
websites/staging/directory/trunk/content/api/user-guide/7.19-search-result-entry.html
websites/staging/directory/trunk/content/api/user-guide/7.2-add-request.html
websites/staging/directory/trunk/content/api/user-guide/7.20-search-result-reference.html
websites/staging/directory/trunk/content/api/user-guide/7.21-unbind-request.html
websites/staging/directory/trunk/content/api/user-guide/7.3-add-response.html
websites/staging/directory/trunk/content/api/user-guide/7.4-bind-request.html
websites/staging/directory/trunk/content/api/user-guide/7.5-bind-response.html
websites/staging/directory/trunk/content/api/user-guide/7.6-compare-request.html
websites/staging/directory/trunk/content/api/user-guide/7.7-compare-response.html
websites/staging/directory/trunk/content/api/user-guide/7.8-del-request.html
websites/staging/directory/trunk/content/api/user-guide/7.9-del-response.html
websites/staging/directory/trunk/content/api/user-guide/8-ldap-rfcs.html
websites/staging/directory/trunk/content/api/vision.html
websites/staging/directory/trunk/content/articles.html
websites/staging/directory/trunk/content/commercial-support.html
websites/staging/directory/trunk/content/conference-materials.html
websites/staging/directory/trunk/content/contribute.html
websites/staging/directory/trunk/content/escimo/index.html
websites/staging/directory/trunk/content/escimo/news.html
websites/staging/directory/trunk/content/fortress/coding-standards.html
websites/staging/directory/trunk/content/fortress/developer-guide.html
websites/staging/directory/trunk/content/fortress/download/download-sources.html
websites/staging/directory/trunk/content/fortress/downloads.html
websites/staging/directory/trunk/content/fortress/history.html
websites/staging/directory/trunk/content/fortress/index.html
websites/staging/directory/trunk/content/fortress/installation.html
websites/staging/directory/trunk/content/fortress/installation/apacheds.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/apacheds.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/guidelines.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/prerequisites.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-I.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-II.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-III.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-IV.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-IX.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-V.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VI.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VII.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-VIII.html
websites/staging/directory/trunk/content/fortress/installation/apacheds/section-X.html
websites/staging/directory/trunk/content/fortress/installation/linux/guidelines.html
websites/staging/directory/trunk/content/fortress/installation/linux/linux.html
websites/staging/directory/trunk/content/fortress/installation/linux/prerequisites.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-I.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-II.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-III.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-IV.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-IX.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-V.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-VI.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-VII.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-VIII.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-X.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-XI.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-XII.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-XIII.html
websites/staging/directory/trunk/content/fortress/installation/linux/section-XIV.html
websites/staging/directory/trunk/content/fortress/installation/openldap.html
websites/staging/directory/trunk/content/fortress/installation/windows/guidelines.html
websites/staging/directory/trunk/content/fortress/installation/windows/prequesites.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-I.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-II.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-III.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-IV.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-IX.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-V.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-VI.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-VII.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-VIII.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-X.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-XI.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-XII.html
websites/staging/directory/trunk/content/fortress/installation/windows/section-XIII.html
websites/staging/directory/trunk/content/fortress/installation/windows/windows.html
websites/staging/directory/trunk/content/fortress/issues.html
websites/staging/directory/trunk/content/fortress/news.html
websites/staging/directory/trunk/content/fortress/overview.html
websites/staging/directory/trunk/content/fortress/user-guide.html
websites/staging/directory/trunk/content/fortress/user-guide/1-intro-rbac.html
websites/staging/directory/trunk/content/fortress/user-guide/1.1-rbac-explained.html
websites/staging/directory/trunk/content/fortress/user-guide/1.2-what-is-not-rbac.html
websites/staging/directory/trunk/content/fortress/user-guide/1.3-what-rbac-is.html
websites/staging/directory/trunk/content/fortress/user-guide/1.4-why-rbac-is-important.html
websites/staging/directory/trunk/content/fortress/user-guide/1.5-how-to-impl-rbac.html
websites/staging/directory/trunk/content/fortress/user-guide/1.6-go-for-more.html
websites/staging/directory/trunk/content/fortress/user-guide/2-multitenancy.html
websites/staging/directory/trunk/content/fortress/user-guide/2.1-fortress-multitenancy.html
websites/staging/directory/trunk/content/fortress/user-guide/2.2-tradi-multi-instances.html
websites/staging/directory/trunk/content/fortress/user-guide/2.3-multitenancy-under-covers.html
websites/staging/directory/trunk/content/fortress/user-guide/3-configuration.html
websites/staging/directory/trunk/content/fortress/vision.html
websites/staging/directory/trunk/content/index.html
websites/staging/directory/trunk/content/issue-tracking.html
websites/staging/directory/trunk/content/kerby/downloads.html
websites/staging/directory/trunk/content/kerby/index.html
websites/staging/directory/trunk/content/kerby/issues.html
websites/staging/directory/trunk/content/kerby/news.html
websites/staging/directory/trunk/content/kerby/overview.html
websites/staging/directory/trunk/content/kerby/quick-start.html
websites/staging/directory/trunk/content/kerby/user-guide.html
websites/staging/directory/trunk/content/kerby/vision.html
websites/staging/directory/trunk/content/mailing-lists-and-irc.html
websites/staging/directory/trunk/content/mavibot/coding-standards.html
websites/staging/directory/trunk/content/mavibot/developer-guide.html
websites/staging/directory/trunk/content/mavibot/download-old-versions.html
websites/staging/directory/trunk/content/mavibot/downloads.html
websites/staging/directory/trunk/content/mavibot/five-minutes-tutorial.html
websites/staging/directory/trunk/content/mavibot/index.html
websites/staging/directory/trunk/content/mavibot/news.html
websites/staging/directory/trunk/content/mavibot/user-guide.html
websites/staging/directory/trunk/content/mavibot/user-guide/1-introduction.html
websites/staging/directory/trunk/content/mavibot/user-guide/1.1-btree-basics.html
websites/staging/directory/trunk/content/mavibot/user-guide/2-btree-types.html
websites/staging/directory/trunk/content/mavibot/user-guide/3-btree-management.html
websites/staging/directory/trunk/content/mavibot/user-guide/4-btree-operations.html
websites/staging/directory/trunk/content/mavibot/user-guide/5-btree-informations.html
websites/staging/directory/trunk/content/mavibot/user-guide/6-btree-configuration.html
websites/staging/directory/trunk/content/mavibot/user-guide/7-btree-internals.html
websites/staging/directory/trunk/content/mavibot/user-guide/7.1-logical-structure.html
websites/staging/directory/trunk/content/mavibot/user-guide/7.2-physical-storage.html
websites/staging/directory/trunk/content/mavibot/user-guide/7.3-serializations.html
websites/staging/directory/trunk/content/mavibot/user-guide/7.4-updates.html
websites/staging/directory/trunk/content/mavibot/vision.html
websites/staging/directory/trunk/content/original-project-proposal.html
websites/staging/directory/trunk/content/privacy-policy.html
websites/staging/directory/trunk/content/references.html
websites/staging/directory/trunk/content/sources.html
websites/staging/directory/trunk/content/special-thanks.html
websites/staging/directory/trunk/content/studio/changelog.html
websites/staging/directory/trunk/content/studio/developers-guide.html
websites/staging/directory/trunk/content/studio/developers-howtos/developers-howtos.html
websites/staging/directory/trunk/content/studio/developers-howtos/howtos/table-widget.html
websites/staging/directory/trunk/content/studio/download-old-versions.html
websites/staging/directory/trunk/content/studio/downloads.html
websites/staging/directory/trunk/content/studio/faqs.html
websites/staging/directory/trunk/content/studio/index.html
websites/staging/directory/trunk/content/studio/installation-in-eclipse.html
websites/staging/directory/trunk/content/studio/internationalization.html
websites/staging/directory/trunk/content/studio/news.html
websites/staging/directory/trunk/content/studio/screenshots.html
websites/staging/directory/trunk/content/studio/source-repository.html
websites/staging/directory/trunk/content/studio/testimonials.html
websites/staging/directory/trunk/content/studio/update/index.html
websites/staging/directory/trunk/content/studio/update/product/index.html
websites/staging/directory/trunk/content/studio/users-guide.html
websites/staging/directory/trunk/content/team.html
websites/staging/directory/trunk/content/testimonies.html
websites/staging/directory/trunk/content/vision.html
Propchange: websites/staging/directory/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Jul 5 22:34:35 2015
@@ -1 +1 @@
-1688609
+1689297
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/0-community.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/0-community.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/0-community.html Sun Jul 5 22:34:35 2015
@@ -169,10 +169,21 @@
</div>
-<h1 id="0-community">0 - Community</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="0-community">0 - Community<a class="headerlink" href="#0-community" title="Permanent link">¶</a></h1>
<p>This chapter explains how to work with the community around the project. The ASF is a community of volunteers, most of them working out of their working time to get the best possible software available to the users, for free. </p>
<p>As a community, we appreciate feedbacks, bug reports, even criticisms, but we value contributions as the best way to make this collaborative work a better software.</p>
-<h1 id="table-of-content">Table of content</h1>
+<h1 id="table-of-content">Table of content<a class="headerlink" href="#table-of-content" title="Permanent link">¶</a></h1>
<ul>
<li><a href="0.1-reporting-bugs.html">0.1. Reporting Bugs</a></li>
<li><a href="0.2-building-trunks.html">0.2. Building trunks</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/0.1-reporting-bugs.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/0.1-reporting-bugs.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/0.1-reporting-bugs.html Sun Jul 5 22:34:35 2015
@@ -169,15 +169,26 @@
</div>
-<h1 id="01-reporting-bugs">0.1 - Reporting Bugs</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="01-reporting-bugs">0.1 - Reporting Bugs<a class="headerlink" href="#01-reporting-bugs" title="Permanent link">¶</a></h1>
<p>So you found a bug in ApacheDS. Don't worry this is a good thing! We can fix it but need your help. There are different degrees to your ability to help out. Some of you have developer skills so you might be able to write a test case that pin points that bug. </p>
<p>This wiki page shows you how you can help us to help you.</p>
-<h2 id="creating-a-testcase-project-using-the-apacheds-archetype-testcase">Creating a testcase project: using the apacheds-archetype-testcase.</h2>
+<h2 id="creating-a-testcase-project-using-the-apacheds-archetype-testcase">Creating a testcase project: using the apacheds-archetype-testcase.<a class="headerlink" href="#creating-a-testcase-project-using-the-apacheds-archetype-testcase" title="Permanent link">¶</a></h2>
<p>We've created a simple archetype for you to rapidly create a Maven project that fires up ApacheDS in embedded mode within a JUnit testcase. This test case will start up ApacheDS as a server on any available port above 1024 on your machine. You can then use JNDI or the Apache LDAP API going over the wire on that port above 1024. You can also use the ApacheDS core API to access the data directly.</p>
<p>So you can write client code in your test case immediately. Just add your code, tar gzip the project, and attach it to your JIRA issue on the ApacheDS JIRA here:</p>
<p>[https://issues.apache.org/jira/browse/DIRSERVER]</p>
<p>We'll prioritize your bug higher than others and probably fix it rapidly because the problem is isolated thanks to your testcase submission. We will in fact strip out your testcase and add it to our suite of test cases to make sure ApacheDS always passes this integration test you've provided.</p>
-<h3 id="installing-the-apacheds-archetype-testcase">Installing the apacheds-archetype-testcase</h3>
+<h3 id="installing-the-apacheds-archetype-testcase">Installing the apacheds-archetype-testcase<a class="headerlink" href="#installing-the-apacheds-archetype-testcase" title="Permanent link">¶</a></h3>
<p>To use the archetype you'll need to check it out and install it. Here's how you can do that for the leading edge of 2.0.0:</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">documentation</span><span class="o">/</span><span class="n">samples</span><span class="o">/</span><span class="n">trunk</span><span class="o">/</span><span class="n">apacheds</span><span class="o">-</span><span class="n">archetype</span><span class="o">-</span><span class="n">testcase</span>
<span class="n">cd</span> <span class="n">apacheds</span><span class="o">-</span><span class="n">archetype</span><span class="o">-</span><span class="n">testcase</span>
@@ -230,24 +241,22 @@ mvn test
{noformat}
Now you can customize the MinimalTest.java or AdvancedTest.java file to isolate your bug. Open the classes with your favorite editor and goto town. However if you want to pull this project into your IDE and edit it there you can use Maven's IDEA, Eclipse and Netbeans integration to create IDE project descriptors for them. Then you can import this project into your IDE. Here's how:</p>
<p>h4. For IDEA</p>
-<p>{noformat}
-mvn idea:idea
-{noformat}</p>
+<p noformat="noformat">{noformat}
+mvn idea:idea</p>
<p>h4. For Eclipse</p>
-<p>{noformat}
-mvn eclipse:eclipse
-{noformat}</p>
+<p noformat="noformat">{noformat}
+mvn eclipse:eclipse</p>
<p>h4. For Netbeans</p>
<p>See this page: [http://maven.apache.org/guides/mini/guide-ide-netbeans/guide-ide-netbeans.html].</p>
<p>h3. Note about version</p>
<p>Note that this archetype is specific for ApacheDS 1.5.5.</p>
<p>h2. Why a Maven Archetype for Testing?</p>
-<h1 id="easy-and-fast-to-start-integration-testing-apacheds">Easy and fast to start integration testing ApacheDS.</h1>
-<h1 id="we-developers-of-apacheds-can-use-it-ourselves">We (developers of ApacheDS) can use it ourselves.</h1>
-<h1 id="we-want-users-of-apacheds-to-help-us-help-them">We want users of ApacheDS to help us help them.</h1>
-<h1 id="users-need-to-customize-a-project-with-perhaps-additional-dependencies">Users need to customize a project with perhaps additional dependencies.</h1>
-<h1 id="users-can-add-many-test-cases-to-the-project">Users can add many test cases to the project.</h1>
-<h1 id="tests-isolating-custom-bugs-can-be-incorporated-into-our-community-test-suite-for-apacheds">Tests isolating custom bugs can be incorporated into our community test suite for ApacheDS.</h1>
+<h1 id="easy-and-fast-to-start-integration-testing-apacheds">Easy and fast to start integration testing ApacheDS.<a class="headerlink" href="#easy-and-fast-to-start-integration-testing-apacheds" title="Permanent link">¶</a></h1>
+<h1 id="we-developers-of-apacheds-can-use-it-ourselves">We (developers of ApacheDS) can use it ourselves.<a class="headerlink" href="#we-developers-of-apacheds-can-use-it-ourselves" title="Permanent link">¶</a></h1>
+<h1 id="we-want-users-of-apacheds-to-help-us-help-them">We want users of ApacheDS to help us help them.<a class="headerlink" href="#we-want-users-of-apacheds-to-help-us-help-them" title="Permanent link">¶</a></h1>
+<h1 id="users-need-to-customize-a-project-with-perhaps-additional-dependencies">Users need to customize a project with perhaps additional dependencies.<a class="headerlink" href="#users-need-to-customize-a-project-with-perhaps-additional-dependencies" title="Permanent link">¶</a></h1>
+<h1 id="users-can-add-many-test-cases-to-the-project">Users can add many test cases to the project.<a class="headerlink" href="#users-can-add-many-test-cases-to-the-project" title="Permanent link">¶</a></h1>
+<h1 id="tests-isolating-custom-bugs-can-be-incorporated-into-our-community-test-suite-for-apacheds">Tests isolating custom bugs can be incorporated into our community test suite for ApacheDS.<a class="headerlink" href="#tests-isolating-custom-bugs-can-be-incorporated-into-our-community-test-suite-for-apacheds" title="Permanent link">¶</a></h1>
<div class="nav">
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/0.2-building-trunks.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/0.2-building-trunks.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/0.2-building-trunks.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="02-building-trunks">0.2 - Building Trunks</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="02-building-trunks">0.2 - Building Trunks<a class="headerlink" href="#02-building-trunks" title="Permanent link">¶</a></h1>
<p>This page give some information about the layout of <em>Apache DS 2.0</em> trunks, and try to explain how it is built.</p>
<div class="toc">
<ul>
@@ -209,29 +220,29 @@
</li>
</ul>
</div>
-<h2 id="project-hierarchy">Project Hierarchy</h2>
+<h2 id="project-hierarchy">Project Hierarchy<a class="headerlink" href="#project-hierarchy" title="Permanent link">¶</a></h2>
<p>The server is a composition of many projects, which should be built in a given order, assuming you want to build the trunk. This order is enforced by a top level pom, so you don't need to take care of this at all. </p>
<p>We will expose the projects hierarchy, just for information.</p>
-<h3 id="project-project">Project project</h3>
+<h3 id="project-project">Project project<a class="headerlink" href="#project-project" title="Permanent link">¶</a></h3>
<p>We first have a meta-project, which contains mainly information about the maven plugins we use. This meta-project is used by all the real projects. This project has one single module : </p>
<ul>
<li>project</li>
</ul>
-<h3 id="checkstyle-configuration-project">Checkstyle-Configuration project</h3>
+<h3 id="checkstyle-configuration-project">Checkstyle-Configuration project<a class="headerlink" href="#checkstyle-configuration-project" title="Permanent link">¶</a></h3>
<p>This project is used to define the checkstyle configuration we use when we generate the reports.</p>
<p>It has one single module :</p>
<ul>
<li>checkstyle-configuration </li>
</ul>
<p><em>Dependencies</em> : project</p>
-<h2 id="junit-addons-project">Junit-Addons project</h2>
-<p>This project is used to add concurrent tests in the server. It's a fork of <a href="ref%20needed">Mycila</a>.</p>
+<h2 id="junit-addons-project">Junit-Addons project<a class="headerlink" href="#junit-addons-project" title="Permanent link">¶</a></h2>
+<p>This project is used to add concurrent tests in the server. It's a fork of <a href="ref needed">Mycila</a>.</p>
<p>It has one single module :</p>
<ul>
<li>junit-addons</li>
</ul>
<p><em>Dependencies</em> : project</p>
-<h3 id="apache-directory-ldap-api-project-formerly-known-as-shared">Apache Directory LDAP API project (formerly known as "Shared")</h3>
+<h3 id="apache-directory-ldap-api-project-formerly-known-as-shared">Apache Directory LDAP API project (formerly known as "Shared")<a class="headerlink" href="#apache-directory-ldap-api-project-formerly-known-as-shared" title="Permanent link">¶</a></h3>
<p>This project contains all the common LDAP structures that are used by ApacheDS, Apache Studio and the Apache LDAP API. In fact, this is the Apache LDAP API (even if we do have slightly more than necessary for an LDAP API).</p>
<p>This project depends on 'project'.</p>
<p>Here is its hierarchy :</p>
@@ -272,8 +283,8 @@
</li>
</ul>
<p><em>Dependencies</em> : project, junit-addons</p>
-<h3 id="jdbm-project">JDBM project</h3>
-<p>This project covers the JDBM code. It's a fork of the <a href="ref%20needed">JDBM 1.0 project</a>.</p>
+<h3 id="jdbm-project">JDBM project<a class="headerlink" href="#jdbm-project" title="Permanent link">¶</a></h3>
+<p>This project covers the JDBM code. It's a fork of the <a href="ref needed">JDBM 1.0 project</a>.</p>
<p>The current project hierarchy is the following :</p>
<ul>
<li>apacheds-jdbm-parent<ul>
@@ -283,7 +294,7 @@
</li>
</ul>
<p><em>Dependencies</em> : project, junit-addons</p>
-<h3 id="apacheds-project">ApacheDS project</h3>
+<h3 id="apacheds-project">ApacheDS project<a class="headerlink" href="#apacheds-project" title="Permanent link">¶</a></h3>
<p>This project is the server itself. It depends on 'project', 'shared' and 'jdbm'.</p>
<p>The current project hierarchy is the following (as of 2.0.0-M9-SNAPSHOT) :</p>
<ul>
@@ -346,7 +357,7 @@
</li>
</ul>
<p><em>Dependencies</em> : project, junit-addons jdbm, shared,</p>
-<h2 id="prerequisites-for-building">Prerequisites for building</h2>
+<h2 id="prerequisites-for-building">Prerequisites for building<a class="headerlink" href="#prerequisites-for-building" title="Permanent link">¶</a></h2>
<p>You must have installed <strong>Maven 3.0.4</strong> and have a <strong>JDK 5</strong> (or a more recent one) installed on your computer. A working internet connection is also mandatory, unless you have all the needed dependences and plugins loaded locally.</p>
<DIV class="note" markdown="1">
If the build hangs or you get an out of memory exception please increase the heap space:
@@ -361,7 +372,7 @@ If the build hangs or you get an out of
mvn clean install
</DIV>
-<h3 id="maven">Maven</h3>
+<h3 id="maven">Maven<a class="headerlink" href="#maven" title="Permanent link">¶</a></h3>
<p><a href="http://maven.apache.org/download.html">Download</a> and install Maven 3.0.4.</p>
<p>Add a MAVEN_HOME environment variable and add MAVEN_HOME/bin to your system path:</p>
<p>On a Linux box you could add the following to the .bashrc file (.bashrc is a file you'll find in your home directory)</p>
@@ -373,13 +384,13 @@ If the build hangs or you get an out of
<p>Windows users, use Control Panel -> System -> Advanced -> Environment Variables</p>
-<h3 id="jdk-5">JDK 5</h3>
+<h3 id="jdk-5">JDK 5<a class="headerlink" href="#jdk-5" title="Permanent link">¶</a></h3>
<DIV class="note" markdown="1">
There may be some issues with older JDK versions and Kerberos, therefore we recommend using a version >=1.5.0_09
</DIV>
<p>Any newer version should also work.</p>
-<h2 id="getting-the-code">Getting the code</h2>
+<h2 id="getting-the-code">Getting the code<a class="headerlink" href="#getting-the-code" title="Permanent link">¶</a></h2>
<p>To download the sources from trunk, you must have installed a <strong>Subversion</strong> client.</p>
<p>With readonly access :</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">apacheds</span><span class="o">/</span><span class="n">trunk</span><span class="o">-</span><span class="n">with</span><span class="o">-</span><span class="n">dependencies</span> <span class="n">apacheds</span><span class="o">-</span><span class="n">trunk</span>
@@ -391,14 +402,14 @@ There may be some issues with older JDK
</pre></div>
-<h2 id="building-the-trunks">Building the trunks</h2>
+<h2 id="building-the-trunks">Building the trunks<a class="headerlink" href="#building-the-trunks" title="Permanent link">¶</a></h2>
<p>You may either specify the profile at the command-line, each time you use 'mvn', or you may configure the profile to always be active.</p>
<p>To use a profile at the command-line:</p>
<div class="codehilite"><pre><span class="c"># mvn -Papache [options] [<goal(s)>] [<phase(s)>]</span>
</pre></div>
-<h3 id="building-the-trunks_1">Building the trunks</h3>
+<h3 id="building-the-trunks_1">Building the trunks<a class="headerlink" href="#building-the-trunks_1" title="Permanent link">¶</a></h3>
<p>Now, we can compile the projects.</p>
<p>The command is simple :</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">apacheds</span><span class="o">-</span><span class="n">trunk</span>
@@ -425,7 +436,7 @@ If you want to do really safe build, run
mvn install -Dintegration
</DIV>
-<h2 id="running-the-server-without-building-installers">Running the server without building installers</h2>
+<h2 id="running-the-server-without-building-installers">Running the server without building installers<a class="headerlink" href="#running-the-server-without-building-installers" title="Permanent link">¶</a></h2>
<p>The server can be run without building any installers. This is helpful during development
(and also can be run for regular purpose as well) </p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">apacheds</span><span class="o">-</span><span class="n">trunk</span><span class="o">/</span><span class="n">apacheds</span><span class="o">/</span><span class="n">service</span>
@@ -435,7 +446,7 @@ If you want to do really safe build, run
<p>To start the server in remote debug mode pass -debug flag. The JDWP socket will be listening
on port 8008.</p>
-<h2 id="building-the-installers">Building the installers</h2>
+<h2 id="building-the-installers">Building the installers<a class="headerlink" href="#building-the-installers" title="Permanent link">¶</a></h2>
<p>Building the installers is a two phase process :</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">apacheds</span><span class="o">-</span><span class="n">trunk</span>
<span class="n">mvn</span> <span class="o">-</span><span class="n">Pinstallers</span> <span class="n">install</span>
@@ -443,7 +454,7 @@ on port 8008.</p>
<p>That's it, the jars will be find in target/images/apacheds-2.0.0-M?-SNAPSHOT-<XXXXXX>-setup.jar where XXXXXX is your local system and M? is the milestone release number for the 2.0 branch.</p>
-<h2 id="starting-the-server-without-installation">Starting the server without installation</h2>
+<h2 id="starting-the-server-without-installation">Starting the server without installation<a class="headerlink" href="#starting-the-server-without-installation" title="Permanent link">¶</a></h2>
<p>The directory apacheds-trunk/installers/apacheds-noarch contains a script for Linux (apacheds.sh) and one for Windows (apacheds.bat) which can be used for starting the server without the need to install it first (as non-root-user on Linux and non-Windows-service on Windows).</p>
<p>Linux:</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">apacheds</span><span class="o">-</span><span class="n">trunk</span><span class="o">/</span><span class="n">installers</span><span class="o">/</span><span class="n">apacheds</span><span class="o">-</span><span class="n">noarch</span>
@@ -451,19 +462,19 @@ on port 8008.</p>
</pre></div>
-<h2 id="eclipse">Eclipse</h2>
+<h2 id="eclipse">Eclipse<a class="headerlink" href="#eclipse" title="Permanent link">¶</a></h2>
<p>As Apache Studio is an Eclipse plugin/RCP application, we use extensively this IDE. Of course, you can use another IDE.</p>
-<h3 id="building-eclipse-files">Building eclipse files</h3>
+<h3 id="building-eclipse-files">Building eclipse files<a class="headerlink" href="#building-eclipse-files" title="Permanent link">¶</a></h3>
<p>To build the .project and .classpath files for eclipse, type the following commands :</p>
<div class="codehilite"><pre><span class="n">cd</span> <span class="n">apacheds</span><span class="o">-</span><span class="n">trunk</span>
<span class="n">mvn</span> <span class="n">eclipse</span><span class="p">:</span><span class="n">eclipse</span>
</pre></div>
-<h3 id="maven-settings">Maven settings</h3>
+<h3 id="maven-settings">Maven settings<a class="headerlink" href="#maven-settings" title="Permanent link">¶</a></h3>
<p>Don't forget to declare a classpath variable named M2_REPO, pointing to ~/.m2/repository, otherwise many links to existing jars will be broken.</p>
<p>You can declare new variables in Eclipse in <em>Windows -> Preferences...</em> and selecting <em>Java -> Build Path -> Classpath Variables</em></p>
-<h3 id="eclipse-hints">Eclipse hints</h3>
+<h3 id="eclipse-hints">Eclipse hints<a class="headerlink" href="#eclipse-hints" title="Permanent link">¶</a></h3>
<p>Add an eclipse-apacheDS.sh file in your eclipse root directory, to allow eclipse to get more memory (e.g. 750MB)
You may also declare a specific workspace when launching eclipse. I have created a workspace-apacheDS directory in my HOME directory, where all the ApacheDS project is built when I use Eclipse.</p>
<div class="codehilite"><pre><span class="o"><</span><span class="n">eclipse_root</span><span class="o">>/</span><span class="n">eclipse</span> <span class="o">-</span><span class="n">data</span> $<span class="n">HOME</span><span class="o">/</span><span class="n">workspace</span><span class="o">-</span><span class="n">apacheDS</span> <span class="o">-</span><span class="n">vm</span> <span class="n">java</span> <span class="o">-</span><span class="n">vmargs</span> <span class="o">-</span><span class="n">Xmx750M</span>
@@ -475,7 +486,7 @@ You may also declare a specific workspac
</pre></div>
-<h3 id="coding-standards">Coding standards</h3>
+<h3 id="coding-standards">Coding standards<a class="headerlink" href="#coding-standards" title="Permanent link">¶</a></h3>
<p>The coding standards including an eclipse code formatting profile is available <a href="../coding-standards.html">here</a></p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/0.3-contributing.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/0.3-contributing.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/0.3-contributing.html Sun Jul 5 22:34:35 2015
@@ -169,8 +169,19 @@
</div>
-<h1 id="03-contributing">0.3 - Contributing</h1>
-<h1 id="join-the-apache-directory-community">Join the Apache Directory Community</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="03-contributing">0.3 - Contributing<a class="headerlink" href="#03-contributing" title="Permanent link">¶</a></h1>
+<h1 id="join-the-apache-directory-community">Join the Apache Directory Community<a class="headerlink" href="#join-the-apache-directory-community" title="Permanent link">¶</a></h1>
<p>The Apache Directory Project is an <a href="http://www.opensource.org">Open Source</a> volunteer project under the auspices of <a href="http://www.apache.org">The Apache Software Foundation (ASF)</a>. We welcome your input and contributions - either with direct participation (coding, documenting, answering questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc..). You can also contribute to <a href="http://www.apache.org">The Apache Software Foundation (ASF)</a> by <a href="http://apache.org/foundation/contributing.html">resource donations</a> (money, time, publicity, hardware, software, conference presentations, speeches, etc...) of through <a href="http://apache.org/foundation/sponsorship.html">the sponsorship program</a> .</p>
<p>To begin with, we suggest you to subscribe to the <a href="http://directory.apache.org/mailing-lists-and-irc.html">Directory Mailing Lists & IRC</a> (follow the link for information on how to subscribe and to access the mail list archives). Listen-in for a while, to see how others make contributions.</p>
<p>Then you can :</p>
@@ -181,7 +192,7 @@
<li>Investigate bugs that have been reported and provide patches where appropriate.</li>
<li>Help with development for the next release of the Directory project and subprojects.</li>
</ul>
-<h2 id="what-we-are-looking-for">What we are looking for</h2>
+<h2 id="what-we-are-looking-for">What we are looking for<a class="headerlink" href="#what-we-are-looking-for" title="Permanent link">¶</a></h2>
<ul>
<li>Source code and fixes contributions</li>
<li>Documentation assistance</li>
@@ -189,7 +200,7 @@
<li>Detailed and constructive feedback</li>
<li>Articles and white papers</li>
</ul>
-<h2 id="how-do-i-contribute">How do I contribute</h2>
+<h2 id="how-do-i-contribute">How do I contribute<a class="headerlink" href="#how-do-i-contribute" title="Permanent link">¶</a></h2>
<ul>
<li>To discuss Apache Directory topics check out the <a href="http://directory.apache.org/mailing-lists-and-irc.html">mailing lists</a>.</li>
<li>Informal discussion also occurs on the <a href="irc://irc.freenode.net/apache-directory">#apache-directory</a> Users IRC channel or on the <a href="irc://irc.freenode.net/apache-directory-dev">#apache-directory-dev</a> Developers IRC channel on <a href="http://freenode.net">freenode.net</a>.</li>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/1-architecture.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1-architecture.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1-architecture.html Sun Jul 5 22:34:35 2015
@@ -169,9 +169,20 @@
</div>
-<h1 id="1-architecture">1 - Architecture</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="1-architecture">1 - Architecture<a class="headerlink" href="#1-architecture" title="Permanent link">¶</a></h1>
<p>We will now describe the server architecture, in order to give you a more deeper understanding of the way the server works.</p>
-<h2 id="chapter-content">Chapter content</h2>
+<h2 id="chapter-content">Chapter content<a class="headerlink" href="#chapter-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="1.1-architecture-overview.html">1.1 - Architectural Overview</a></li>
<li><a href="1.2-network.html">1.2 - Network Layer</a></li>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.1-architecture-overview.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.1-architecture-overview.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.1-architecture-overview.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="11-architecture-overview">1.1 - Architecture Overview</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="11-architecture-overview">1.1 - Architecture Overview<a class="headerlink" href="#11-architecture-overview" title="Permanent link">¶</a></h1>
<p>The Apache Directory Server (aka <em>ApacheDS</em>) architecture has many different layers. The following schema expose the most important ones :</p>
<p><img alt="ApacheDS architecture" src="images/architecture.png" /></p>
<p>As we can see, we distinguish four different layers :</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.2-network.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.2-network.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.2-network.html Sun Jul 5 22:34:35 2015
@@ -169,7 +169,18 @@
</div>
-<h1 id="12-network-layer">1.2 - Network Layer</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="12-network-layer">1.2 - Network Layer<a class="headerlink" href="#12-network-layer" title="Permanent link">¶</a></h1>
<p>This layer is the part the user connects to when he wants to obtain some data from the server. This is not a mandatory part of the server : we don't need to use it when the server is embedded.</p>
<p>We offer more than just LDAP protocol, the server also include various protocols :</p>
<ul>
@@ -181,23 +192,23 @@
</ul>
<p>Not all of them are implemented in the current version, but at least the Kerberos server is available. The other protocols have been developed as a proof of concept : as they are all depending upon a storage database, we have used the LDAP server as a storage.</p>
<p>It's perfectly possible to imagine more protocols being implemented in the near future...</p>
-<h2 id="server-startup">Server startup</h2>
+<h2 id="server-startup">Server startup<a class="headerlink" href="#server-startup" title="Permanent link">¶</a></h2>
<p>This chapter title is a bit misleading. We don't start a server, we start a <em>DirectoryService</em>, then we start various servers on top of it.
The <em>DirectoryService</em> is the part responsible for the management of data (retrieval, storage, etc). All the servers can access this storage if needed.</p>
<p>So when the <em>DirectoryService</em> has been started and is operational, we can start the various servers, which will accept incoming requests from remote peers.</p>
-<h3 id="transports">Transports</h3>
+<h3 id="transports">Transports<a class="headerlink" href="#transports" title="Permanent link">¶</a></h3>
<p>We allow connection through the definition of <em>transports</em>. A <em>Transport</em> is a <strong>TCP</strong> or an <strong>UDP</strong> socket capable of absorbing a request and to send a response. Depending on the type of server, we may declare one or more <strong>TCP</strong> <em>Transports</em>, or a <strong>TCP</strong> and a <strong>UDP</strong> <em>Transports</em>, or an <strong>UDP</strong> <em>Transport</em> only.</p>
-<h3 id="ldap-server">Ldap Server</h3>
+<h3 id="ldap-server">Ldap Server<a class="headerlink" href="#ldap-server" title="Permanent link">¶</a></h3>
<p>The LDAP server needs one or two <strong>TCP</strong> <em>Transport</em>. We have the standard <em>LDAP</em> port (defaulting to <em>10389</em> for <em>ApacheDS</em>, but the well know port is usually 389), and one can also declare the <em>LDAPS</em> port (defaulting to <em>10636</em> for <em>ApacheDS</em>, but the well know port is usually 636). </p>
<DIV class="warning" markdown="1">
Note that *LDAPS* is considered as deprecated.
</DIV>
-<h3 id="kerberos-server">Kerberos Server</h3>
+<h3 id="kerberos-server">Kerberos Server<a class="headerlink" href="#kerberos-server" title="Permanent link">¶</a></h3>
<p>The Kerberos Server uses one <strong>TCP</strong> <em>Transport</em> (defaulting to <em>60088</em>, but the well know port is 88 ) and one <strong>UDP</strong> _transport (same value for both ports). The idea is that the communication starts on <strong>TCP</strong> and continues on <strong>UDP</strong>.</p>
-<h3 id="changepassword-server">ChangePassword Server</h3>
+<h3 id="changepassword-server">ChangePassword Server<a class="headerlink" href="#changepassword-server" title="Permanent link">¶</a></h3>
<p>The ChangePassword Server uses one <strong>TCP</strong> <em>Transport</em> and one <strong>UDP</strong> transport, too. The default value is <em>60464</em>, but the well known port is <em>464</em>.</p>
-<h3 id="http-server">Http Server</h3>
+<h3 id="http-server">Http Server<a class="headerlink" href="#http-server" title="Permanent link">¶</a></h3>
<p>We have a HttpServer running too, it's used for management. The declared ports are both <strong>TCP</strong> port, one is for HTTP and its default value is <em>8080</em>, the other one is for HTTPS and its default value is <em>8443</em>.</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.3-directory-service.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.3-directory-service.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.3-directory-service.html Sun Jul 5 22:34:35 2015
@@ -169,13 +169,24 @@
</div>
-<h1 id="13-directoryservice">1.3 - DirectoryService</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="13-directoryservice">1.3 - DirectoryService<a class="headerlink" href="#13-directoryservice" title="Permanent link">¶</a></h1>
<p>The <em>DirectoryService</em> is the core of the server. This is where we process incoming requests and ask the backend for data. </p>
<p>It has an entry point, the <em>OperationManager</em>, which is in charge of pushing the requests into the <em>Interceptors</em> chain, and to protect the server against concurrent modifications.</p>
<p>Then the request is going through every <em>Interceptor</em> being registered for this operation. When we have gone through all the <em>Interceptors</em>, we have reached the <em>PartitionNexus</em>, which is the connection with the backends.</p>
<p>We now just have to determinate which type of <em>Backend</em> we should address, and this is done using the <em>Dn</em>. The request is then transmitted to the <em>Backend</em>, which returns the result.</p>
<p>The result bubbles up through the <em>Interceptors</em> as we unfold the stack stack, up to the <em>OperationManager</em> and to the caller.</p>
-<h2 id="environment">Environment</h2>
+<h2 id="environment">Environment<a class="headerlink" href="#environment" title="Permanent link">¶</a></h2>
<p>The <em>DirectoryService</em> knows about its execution environment : it has a <em>schemaManager</em> instance, it knows about the <em>Interceptors</em> chain, it stores a map of all the pending requests (it's necessary as one may abandon some request), it holds the existing <em>Sessions</em>.</p>
<p>In other word, the <em>DirectoryService</em> is not only the part of the server executing the logic, it also holds the current state of every clients.</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.4-interceptors.html Sun Jul 5 22:34:35 2015
@@ -169,12 +169,23 @@
</div>
-<h1 id="14-interceptors">1.4 - Interceptors</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="14-interceptors">1.4 - Interceptors<a class="headerlink" href="#14-interceptors" title="Permanent link">¶</a></h1>
<p><em>Interceptors</em> are functional layers inside the <em>DirectoryService</em>. Each one of them are responsible for a specific task. They are ordered, and this order is not to be changed.</p>
<p>Each operation rceived by the <em>DirectoryService</em> will be processed by various interceptors, one after the other, down to the backend, and again when the result comes back to the caller. An <em>interceptor</em> can call the next <em>interceptor</em>, whcih will be determinated by the position it has in the chain of <em>interceptors</em>, or simply return. Note that calling the next <em>interceptor</em> does not require that you know which one will be called.</p>
<p>Some <em>Interceptors</em> can be disabled, some other can be enabled. It's also possible to add some new one.</p>
<p>All in all, they will handle operations from a specific functional aspect.</p>
-<h2 id="handled-operations">Handled operations</h2>
+<h2 id="handled-operations">Handled operations<a class="headerlink" href="#handled-operations" title="Permanent link">¶</a></h2>
<p>Each <em>Interceptor</em> handles a subset of the possible operations, among those listed in the following table :</p>
<table>
<thead>
@@ -239,7 +250,7 @@
</tbody>
</table>
<p>It is important to understand that each operation will go through each <em>Interceptor</em> declared to handle the operation, down to the backend.</p>
-<h2 id="existing-interceptors">Existing interceptors</h2>
+<h2 id="existing-interceptors">Existing interceptors<a class="headerlink" href="#existing-interceptors" title="Permanent link">¶</a></h2>
<p>The following interceptors are already present in the server, even if they are not enabled.
In this table, we list all the operations each interceptor is handling, and if the <em>interceptor</em> is enabled by default or not :</p>
<table>
@@ -810,7 +821,7 @@ In this table, we list all the operation
</tbody>
</table>
<p>The operations that are available are the operations for which we have some implementation in the interceptor class. For instance, the <em>JournalInterceptor</em> class implement the <em>add</em>, <em>delete</em>, <em>modify</em>, <em>move</em>, <em>moveAndRename</em> and <em>rename</em> methods.</p>
-<h2 id="interceptors-order">Interceptors order</h2>
+<h2 id="interceptors-order">Interceptors order<a class="headerlink" href="#interceptors-order" title="Permanent link">¶</a></h2>
<p>As we already said, the <em>Interceptors</em> order is significant : why would we proceed an <em>Add</em> operation through all the <em>Interceptors</em> if the user is simply denied the right to add an entry by the <em>AciAuthorizationInterceptor</em> ?</p>
<p>Currently, the following order is enforced :</p>
<table>
@@ -879,7 +890,7 @@ In this table, we list all the operation
</tr>
</tbody>
</table>
-<h2 id="example">Example</h2>
+<h2 id="example">Example<a class="headerlink" href="#example" title="Permanent link">¶</a></h2>
<p>Let's consider the <em>search</em> operation. It will be processed successively by the following <em>Interceptors</em>, as it can be deduced by the two previous tables :</p>
<ul>
<li>NormalizationInterceptor</li>
@@ -891,7 +902,7 @@ In this table, we list all the operation
<li>SubentryInterceptor</li>
</ul>
<p>We can do the same exercise for each operation.</p>
-<h2 id="processing">Processing</h2>
+<h2 id="processing">Processing<a class="headerlink" href="#processing" title="Permanent link">¶</a></h2>
<p>Basically, an <em>Interceptor</em> receives a request for an operation, does some pre-processing, calls the next <em>Interceptor</em> in the chain, does some post-processing, and returns a result.</p>
<p>Calling the next <em>Interceptor</em> is as simple as calling the <em>next(OperationContext)</em> method, which will compute the right <em>Interceptor</em>.</p>
<p>The pre-processing and post-processing are standard Java code, there is nothing special there. </p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/1.5-backend.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/1.5-backend.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/1.5-backend.html Sun Jul 5 22:34:35 2015
@@ -169,36 +169,47 @@
</div>
-<h1 id="15-backend">1.5 - Backend</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="15-backend">1.5 - Backend<a class="headerlink" href="#15-backend" title="Permanent link">¶</a></h1>
<p>The <em>Backend</em> is the part of the server responsible for storing data in a way we can easily retrieve them. This storage does not necessarily have to be remanent : we can have a in-memory <em>backend</em>.</p>
-<h2 id="existing-backends">Existing Backends</h2>
+<h2 id="existing-backends">Existing Backends<a class="headerlink" href="#existing-backends" title="Permanent link">¶</a></h2>
<p>We currently have 3 different backends :</p>
<ul>
<li>JDBM</li>
<li>LDIF</li>
<li>In-Memory</li>
</ul>
-<h3 id="jdbm-backend">JDBM Backend</h3>
+<h3 id="jdbm-backend">JDBM Backend<a class="headerlink" href="#jdbm-backend" title="Permanent link">¶</a></h3>
<p>The <strong>JDBM</strong> backend is storing data on disk, using <strong>BTrees</strong>. It's fast when it comes to retrieve data, slow when you have to add them.</p>
-<h3 id="in-memory-backend">In-Memory Backend</h3>
+<h3 id="in-memory-backend">In-Memory Backend<a class="headerlink" href="#in-memory-backend" title="Permanent link">¶</a></h3>
<p>This Backend loads in memory a full set of entries. ALl of them must be hold by the existig memory, we don't write on disk anything nor we read anything from disk. If the server is stopped, everything is lost.</p>
-<h3 id="ldif-backend">LDIF Backend</h3>
+<h3 id="ldif-backend">LDIF Backend<a class="headerlink" href="#ldif-backend" title="Permanent link">¶</a></h3>
<p>It comes in two forms : one single file, or many fles (one per entry). It's always backed by a in-memory <em>Backend</em>, otherwise it would not be possible to retrieve the entries. </p>
<p>As we depend on a in-memory backend, which handles the indexes, we have to create those indexes when this <em>Backend</em> is read, which can be a costly operation. </p>
-<h3 id="future-backends">Future Backends</h3>
+<h3 id="future-backends">Future Backends<a class="headerlink" href="#future-backends" title="Permanent link">¶</a></h3>
<p>We intend to add another in-memory backend, based on <em>Mavibot</em>, a <strong>MVCC BTREE</strong>. The biggest advantage over the other systems is that it's fast, it allows concurrent reads without locks when the other <em>Backend</em> block the reads when some write operation is being processed. Also it saves on disk it contents periodically, and has a Journal so that we can recover from a crash.</p>
<p>The only drawback is that all the entries and indexes must hold in memory. On the other hand, we don't anymore need a cache.</p>
-<h2 id="how-it-works">How it works</h2>
+<h2 id="how-it-works">How it works<a class="headerlink" href="#how-it-works" title="Permanent link">¶</a></h2>
<p>Basically, each <em>Backend</em> instance inherit from the <em>AbstractBTreePartition</em> class. We can see that a <em>Backend</em> <strong>must</strong> be a <strong>Btree</strong>.</p>
<p>Data are stored into various tables. In fact, we have one table containing all the entries - the <strong>MasterTable</strong> - and many indexes. </p>
-<h3 id="mastertable">MasterTable</h3>
+<h3 id="mastertable">MasterTable<a class="headerlink" href="#mastertable" title="Permanent link">¶</a></h3>
<p>The <em>MasterTable</em> contains all the entries, serialized. </p>
<p>This table is a <Key, Value> <strong>BTree</strong>, where the key is the entry's <strong>UUID</strong>, and the value the serialized entry.</p>
<DIV class="note" markdown="1">
Theoretically, we could be able to read it, and restore the whole database, indexes included, assuming that we know which index we have to create. Sadly, it's not enough, as the entries are stored without any information about their position in the **DIT**.
</DIV>
-<h3 id="indexes">Indexes</h3>
+<h3 id="indexes">Indexes<a class="headerlink" href="#indexes" title="Permanent link">¶</a></h3>
<p>Each index is also a <key, value> <strong>BTree</strong>, with some exceptions : as we may store multi-valued elements, it's perfectly possible that the value will grow up to a point it's extremely costly to store it serialized. For instance, the <em>ObjectClass</em> index may have thousands of entries for the <em>Person</em> key.</p>
<p>In this case, we use a sub-btree, which is a <key,key> <strong>BTree</strong> (as strange as it sounds, it's an easy way to add a new key without having to rewrite the full value).</p>
<p>The key can be a <em>String</em>, or a <em>ParentIdAndRdn</em>.</p>
@@ -213,7 +224,7 @@ Theoretically, we could be able to read
<li>SubAlias : An index used of descendant aliases</li>
</ul>
<p>The user may define many different indexes, depending on his or her needs.</p>
-<h3 id="the-parentidandrdn-index">The ParentIdAndRdn index</h3>
+<h3 id="the-parentidandrdn-index">The ParentIdAndRdn index<a class="headerlink" href="#the-parentidandrdn-index" title="Permanent link">¶</a></h3>
<p>This index is special, as it's used to associate an entry to a position in the <strong>DIT</strong>. Assuming that each entry has a <em>Dn</em>, and that this <em>Dn</em> describes a hierarchy, the <em>ParentIdAndRdn</em> index depicts this hierarchy.</p>
<p>The <em>ParentId</em> part refers to the <em>UUID</em> of the parent for the current entry. The <em>Rdn</em> part is the entry <em>Rdn</em>. In order to rebuild the full <em>Dn</em> for a given entry, we must get all the <em>ParentIdAndRdn</em> up to the root to grab all the needed <em>Rdn</em>.</p>
<p>This index is also used to process one level and sub level indexes.</p>
Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html
==============================================================================
--- websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html (original)
+++ websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html Sun Jul 5 22:34:35 2015
@@ -169,13 +169,24 @@
</div>
-<h1 id="2-server-configuraion">2 - Server Configuraion</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="2-server-configuraion">2 - Server Configuraion<a class="headerlink" href="#2-server-configuraion" title="Permanent link">¶</a></h1>
<p>We will now describe the server configuration. Usually, all the configuration changes
are done using Apache Directory Studio, which offers a pretty GUI. One can also update
server configuration using LDAP operations, as the configuration is stored in the <strong>DIT</strong>.
Note that the server must be restarted after modifying the configuration.</p>
<p>We will then describe the installation layout (ie, how the various files are stored on the disk).</p>
-<h2 id="chapter-content">Chapter content</h2>
+<h2 id="chapter-content">Chapter content<a class="headerlink" href="#chapter-content" title="Permanent link">¶</a></h2>
<ul>
<li><a href="2.1-config-description.html">2.1 - Configuration Description</a></li>
<li><a href="2.2-instance-layout.html">2.2 - Instance Layout</a><ul>