directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From smckin...@apache.org
Subject svn commit: r1776795 - /directory/site/trunk/content/api/user-guide/
Date Sat, 31 Dec 2016 16:42:10 GMT
Author: smckinney
Date: Sat Dec 31 16:42:10 2016
New Revision: 1776795

URL: http://svn.apache.org/viewvc?rev=1776795&view=rev
Log:
more corrections

Modified:
    directory/site/trunk/content/api/user-guide/2.10-ldap-connection-template.mdtext
    directory/site/trunk/content/api/user-guide/2.11-filter-builder.mdtext
    directory/site/trunk/content/api/user-guide/4-schema-management.mdtext
    directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext
    directory/site/trunk/content/api/user-guide/4.2.1.1-attribute-types.mdtext
    directory/site/trunk/content/api/user-guide/4.2.1.2-object-classes.mdtext
    directory/site/trunk/content/api/user-guide/4.2.1.3-syntaxes.mdtext
    directory/site/trunk/content/api/user-guide/4.2.1.4-matching-rules.mdtext
    directory/site/trunk/content/api/user-guide/4.2.1.8-name-forms.mdtext

Modified: directory/site/trunk/content/api/user-guide/2.10-ldap-connection-template.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/2.10-ldap-connection-template.mdtext?rev=1776795&r1=1776794&r2=1776795&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/2.10-ldap-connection-template.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/2.10-ldap-connection-template.mdtext Sat Dec
31 16:42:10 2016
@@ -34,7 +34,7 @@ The LdapConnectionTemplate provides simp
 * [Providing Simplified, Password Policy Aware, Authentication/Password Modification Methods](#providing-simplified-password-policy-aware-authenticationpassword-modification-methods)
 * [Other Useful Methods](#other-useful-methods)
 
-The concept is basically that of the Template Method design pattern in that it does all the
boiler plate work for you and hands back control as necessary.
+Conceptually it uses the Template Method design pattern to do all of the boiler plate work
for you.  It can give control back as needed for special cases.
 
 Managing Connections
 --------------------
@@ -74,12 +74,12 @@ The connection template manages connecti
         new LdapConnectionTemplate( new LdapConnectionPool(
             new ValidatingPoolableLdapConnectionFactory( factory ), poolConfig ) );
 
-This may look like a lot, but most of it is optional and it is the last you will have to
think about connections.
+This may look complicated, but most of the parameters are optional and it's an easy way for
you to manage connections in a safe and efficient manner.
 
 Providing Factory Methods For Model Objects
 -------------------------------------------
 
-The connection template implements an interface called ModelFactory.  Any implementation
of this factory can be injected into the template once it is constructed.  By default, it
uses ModelFactoryImpl which in turn constructs the standard Apache LDAP API model objects.
 This abstractions frees you from having to be concerned with implementation details while
still giving you the power to override the default behavior as you see fit.
+The connection template implements an interface called the ModelFactory.  Any implementation
of this factory can be injected into the template once it is constructed.  By default, it
uses ModelFactoryImpl which in turn constructs the standard Apache LDAP API model objects.
 This abstraction frees you from having to be concerned with implementation details while
still giving you the power to override the default behavior as you see fit.
 
     :::Java
     ModelFactory modelFactory = new MyCustomModelFactory();
@@ -135,7 +135,7 @@ Modify simply supplies the 2 standard ap
             }
         } );
 
-Delete provides the 2 standard approaches plus an additional DN only option as that is most
likely enough:
+Delete provides the 2 standard approaches plus an additional DN-only option as that is most
likely enough:
 
     :::Java
     // using DN only
@@ -167,7 +167,7 @@ More information on EntryMapper can be f
 Handling Search Result Iteration
 --------------------------------
 
-Searching usually contains a lot of boiler plate code for build requests and iterating through
responses.  This template does the work for you. It iterates over the entire result set, feeds
each entry through an EntryMapper, and collects the results into the list returned to the
caller.  All you have to do is provide the EntryMapper for mapping a single entry to a domain
object.  EntryMapper itself is a very simple interface with one method.  As you saw before
in the lookup documentation, they are typically defined as static members of your service
classes:
+Searching usually contains a lot of boilerplate code for building requests and iterating
through its responses.  This template does the work for you. It iterates over the entire result
set, feeds each entry through an EntryMapper, and assembles the results into a list tht is
returned to the caller.  All you have to do is provide the EntryMapper for mapping a single
entry to a domain object.  EntryMapper itself is a very simple interface with one method.
 As you saw before in the lookup documentation, they are typically defined as static members
of your service classes:
 
     :::Java
     // typically mappers are reused, so define a static member
@@ -193,7 +193,7 @@ And now your searches become much simple
         SearchScope.ONELEVEL,
         muppetEntryMapper );
 
-Now that is just plain ***SIMPLE***.  The search method has many overloads to simplify use
as it is the most common LDAP operation.  There is also a searchFirst method which provides
all the same overloads and is designed to return the first matching result:
+Now that is just plain ***SIMPLE***.  The search method has many overloads to simplify usages
for the most common LDAP operations.  There is also a searchFirst method which provides all
the same overloads and is designed to return the first matching result:
 
     :::Java
     Muppet kermit = ldapConnectionTemplate.searchFirst( 
@@ -224,7 +224,7 @@ This has the added benefit of ensuring t
 Providing Simplified, Password Policy Aware, Authentication/Password Modification Methods
 -----------------------------------------------------------------------------------------
 
-One of the most common uses of LDAP is as an identity provider.  As such, the most common
operation is authentication, and password management.  If your LDAP server supports the [password
policy control](http://tools.ietf.org/html/draft-behera-ldap-password-policy-10) then the
authenticate method is very handy:
+One of the most common usages of LDAP is as an identity provider.  As such, the most common
operation is authentication, and password management.  If your LDAP server supports the [password
policy control](http://tools.ietf.org/html/draft-behera-ldap-password-policy-10) then the
authenticate method is very handy:
 
     :::Java
     // throws PasswordException if authentication fails
@@ -241,7 +241,7 @@ One of the most common uses of LDAP is a
 
 In this case, if authentication failed, a PasswordException is thrown.  If authentication
was successful, any warnings will be returned in the PasswordWarning object, or null will
be returned if there are no warnings.
 
-Modifying a password is just as simple:
+Modifying a password is simple as well:
 
     :::Java
     // using administrator account to modify a users password
@@ -259,7 +259,7 @@ If you modify the password as an adminis
 Other Useful Methods
 --------------------
 
-The template provides a method that will check the response and throw an exception if the
request was not successful.  It was designed to be chained:
+The template provides a method that checks the response and throws an exception if the request
was unsuccessful.  It was designed to be chained:
 
     :::Java
     // using DN only

Modified: directory/site/trunk/content/api/user-guide/2.11-filter-builder.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/2.11-filter-builder.mdtext?rev=1776795&r1=1776794&r2=1776795&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/2.11-filter-builder.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/2.11-filter-builder.mdtext Sat Dec 31 16:42:10
2016
@@ -25,7 +25,7 @@ Notice: Licensed to the Apache Software
 2.11 - The FilterBuilder(e)
 ===========================
 
-This class is a builder for constructing well formed search filters according to [RFC 4515](https://tools.ietf.org/html/rfc4515.html).
This builder is most convenient when you use static imports. For example:
+This class is a builder for constructing well formed search filters according to [RFC 4515](https://tools.ietf.org/html/rfc4515.html).
This builder is most convenient when using static imports. For example:
 
      import static org.apache.directory.ldap.client.api.search.FilterBuilder.and;
      import static org.apache.directory.ldap.client.api.search.FilterBuilder.equal;
@@ -47,7 +47,7 @@ This class is a builder for constructing
 ## And filter 
 
 
-Returns a new FilterBuilder that will & together all of the supplied filters. For example:
+Returns a new FilterBuilder that will combine all of the supplied filters with a **logical
AND** (&). For example:
 
     and( equal( "givenName", "kermit" ), equal( "sn", "the frog" ) ).toString()
  
@@ -58,7 +58,7 @@ Which would match all entries with a giv
 
 ## Or filter
 
-Returns a new FilterBuilder that will | together all of the supplied filters. For example:
+Returns a new FilterBuilder that will combine all of the supplied filters with a **logical
OR** (|). For example:
 
     or( equal( "givenName", "kermit" ), equal( "givenName", "walter" ) ).toString()
  
@@ -69,7 +69,7 @@ Which would match any entry with the giv
 
 ## Not filter
 
-Returns a new FilterBuilder for negating another filter. For example:
+Returns a new FilterBuilder for negating another filter (!). For example:
 
     not( present( "givenName" ) ).toString();
  
@@ -114,8 +114,7 @@ Which would match entries with the commo
  
 would result in the string: _(cn:dn:=Kermit The Frog)_
  
-Which would match entries with the common name Kermit The Frog even if the
-common name was only specified as part of the dn.
+Which would match entries with the common name Kermit The Frog even if the common name was
only specified as part of the dn.
 
     extensible( "cn", "Kermit The Frog" )
         .setMatchingRule( "caseExactMatch" )
@@ -123,8 +122,7 @@ common name was only specified as part o
  
 would result in the string: _(cn:caseExactMatch:=Kermit The Frog)_
  
-Which would match entries with the common name Kermit The Frog, using a case
-sensitive matcher.
+Which would match entries with the common name Kermit The Frog, using a case sensitive matcher.
 
     extensible( "cn", "Kermit The Frog" )
         .useDnAttributes()
@@ -133,8 +131,7 @@ sensitive matcher.
  
 would result in the string: _(cn:dn:caseExactMatch:=Kermit The Frog)_
  
-Which would match entries with the common name Kermit The Frog, using a case
-sensitive matcher even if the name was only specified as part of the dn.
+Which would match entries with the common name Kermit The Frog, using a case sensitive matcher
even if the name was only specified as part of the dn.
 
     extensible( "Kermit The Frog" )
         .setMatchingRule( "1.2.3.4.5.6.7" )
@@ -142,8 +139,7 @@ sensitive matcher even if the name was o
  
 would result in the string: _(:1.2.3.4.5.6.7:=Kermit The Frog)_
  
-Which would match entries with any attribute whose value is Kermit The Frog, 
-using the _hypothetical_ matching rule indicated by the oid 1.2.3.4.5.6.7.
+Which would match entries with any attribute whose value is Kermit The Frog, using the _hypothetical_
matching rule indicated by the oid 1.2.3.4.5.6.7.
 
 ## Less Or Equal Filter
 
@@ -177,7 +173,7 @@ Which MIGHT match results whose locality
 
 ## StartsWith Filter
 
-Returns a new FilterBuilder that will construct a SubString filter with an initial part,
zero or more any parts, but no final part. For instance:
+Returns a new FilterBuilder that constructs a SubString filter with an initial part, zero
or more any parts, but no final part. For example:
 
     startsWith( "sn", "Th", "Soft", "Foun" )).toString()
  
@@ -187,7 +183,7 @@ Which would match any entry with an sn s
 
 ## EndsWith Filter
 
-Returns a new FilterBuilder that will construct a SubString filter with no initial part,
zero or more any parts, and a final part. For instance:
+Returns a new FilterBuilder that constructs a SubString filter with no initial part, zero
or more any parts, and a final part. For instance:
 
     endsWith( "sn", "Soft", "Foun", "ion" )).toString()
  
@@ -197,7 +193,7 @@ Which would match any entry with an sn c
 
 ## Contains Filter
 
-Returns a new FilterBuilder that will construct a SubString filter with no initial part,
zero or more any parts, and no final part. For instance:
+Returns a new FilterBuilder that constructs a SubString filter with no initial part, zero
or more any parts, and no final part. For instance:
 
     contains( "sn", "Soft", "Foun" )).toString()
  
@@ -207,7 +203,7 @@ Which would match any entry with an sn c
 
 ## Substring Filter
 
-Returns a new FilterBuilder that will construct a SubString filter with an initial part,
zero or more any parts, and a final part. For instance:
+Returns a new FilterBuilder that constructs a SubString filter with an initial part, zero
or more any parts, and a final part. For instance:
 
     substring( "sn", "The", "Soft", "Foun", "ion" )).toString()
  

Modified: directory/site/trunk/content/api/user-guide/4-schema-management.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/4-schema-management.mdtext?rev=1776795&r1=1776794&r2=1776795&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/4-schema-management.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4-schema-management.mdtext Sat Dec 31 16:42:10
2016
@@ -24,9 +24,9 @@ Notice: Licensed to the Apache Software
 
 # 4 - Schema Management
 
-All the LDAP servers have a schema, and this schema is used to define what are the accepted
elements, and their syntax.
+Every LDAP server necessarily has a schema that's used to define its accepted data elements
along with their rules for usage (syntax).
 
-A LDAP Schema is a complex combinaison of many schema elements. We will define here what
are those schema elements, and how we organize them. Last, not least, we will explain how
to leverage the schema on the client side.
+An LDAP Schema is a complex combination of many schema elements. Here's we'll define those
schema elements and how to organize them. Last, but not least, we'll explain how to leverage
the schema on the client side.
 
 ## Contents
 

Modified: directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext?rev=1776795&r1=1776794&r2=1776795&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4.2-schema-manager.mdtext Sat Dec 31 16:42:10
2016
@@ -24,7 +24,7 @@ Notice: Licensed to the Apache Software
 
 # 4.2 - Schema Manager
 
-The API and the ApacheDS server have to keep the schema elements available. This is done
through what we call the **SchemaManager**. It hides all the internal structure from the users.
+The API and the ApacheDS server components must to keep schema elements available to interroate
and use. This is done through what we call a **SchemaManager**. It hides the internal structure
of the schema objects from the users.
 
 
 ## Contents
@@ -44,18 +44,17 @@ The API and the ApacheDS server have to
 
 ## Introduction
 
-The **SchemaManager** stores all the Schema elements (**[AttributeTypes (e)]()**, **[ObjectClasses
(e)]()**, ... Internally, we store those elements into what we call the **Registries**, which
are hives where each Schema Objects are stored. Each schema element has a dedicated **Registry**.
Think of it as a Map which returns a reference to a specific Schema Element when you know
it's name or its OID.
+The **SchemaManager** stores all the Schema elements (**[AttributeTypes (e)]()**, **[ObjectClasses
(e)]()**, ... Internally, we store these elements into what is call a **Registries**.  Registries
are hives where each Schema Object is stored. Each schema element has a dedicated **Registry**
associated with it. Think of it as a Map which returns a reference to a specific Schema Element
according to its name or OID.
 
-    Note : each Schema Element is properly defined by one of its names or its OID. The OID
is unique across all the schema elements,
-    when the name can be used in different schema element (for instance, the **audio** AttributeType
or ObjectClass)
+    Note : each Schema Element is properly defined by one of its names or OID. The OID must
be unique across all schema elements, when the name can be used in different schema element
(for instance, the **audio** AttributeType or ObjectClass)
 
-From the user point of view, the **SchemaManager** is seen as a representation of the available
LDAP schema elements. It can of course be extended, or modified, by adding or removing some
schema elements. For historic reasons, the schema elements are gathered into what we call
a **schema**. Usually, this is what you load into a **schemaManager**
+From the user point of view, the **SchemaManager** is seen as a representation of the available
LDAP schema elements. It can of course be extended, or modified, by adding or removing schema
elements. For historic reasons, the schema elements are gathered into what we call a **schema**.
Usually, this is what you load into a **schemaManager**
 
-The server has one instance of a **SchemaManager**, which is used internally, and a user
won't control it, in any case. On the client side, we can load a **SchemaManager** either
from the server (and then we have a duplicated instance), or from existing schema files. We
can even create a brand new **SchemaManager** and fill it with all what we need.
+The server has one instance of a **SchemaManager**, which is used internally, and a users
aren't allowed to control it. On the client side, we can load a **SchemaManager** either from
the server (which will be a duplicated instance), or from existing schema files. We can even
create a brand new **SchemaManager** and fill it with anything needed.
 
 ## The various pieces of the puzzle...
 
-Creating a **SchemaManager** results in a complex structure to be created, and involves a
lot of other helper class to be used. We will separate the description in three groups :
+Creating a **SchemaManager** results in a complex structure being created, and involves a
lot of other helper class. We will separate the description into three groups:
 
 * The elements stored in the **SchemaManager**
 * The containers in which those **SchemaObject** instances are stored, called **Registries**
@@ -63,14 +62,14 @@ Creating a **SchemaManager** results in
 
 ## Getting a SchemaManager
 
-The very first thing when you want to have access to the schema elements is to access to
the **SchemaManager**. This can be done in many ways :
+The very first thing we do to access the schema elements is to gain access to the **SchemaManager**.
This can be done in many ways:
 
 * you can create one from scratch, and load it with the elements you want
 * you can use a default **SchemaManager**, with some default schema elements
 * you can create a **SchemaManager**, and load the schema elements from a destination
 * last, not least - and probably the most interesting possibility -, you can connect to a
LDAP server and load the schema from it.
 
-We will show how to proceed in those four use cases.
+We will show how to proceed in each of these four use cases.
 
 
 ## Using a SchemaManager

Modified: directory/site/trunk/content/api/user-guide/4.2.1.1-attribute-types.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/4.2.1.1-attribute-types.mdtext?rev=1776795&r1=1776794&r2=1776795&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/4.2.1.1-attribute-types.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4.2.1.1-attribute-types.mdtext Sat Dec 31
16:42:10 2016
@@ -24,7 +24,7 @@ Notice: Licensed to the Apache Software
 
 # 4.2.1.1 - AttributeTypes
 
-The **AttributeType** **SchemaObject** expose some extra parameters. Here is the description
as found in RFC 4512 :
+The **AttributeType** **SchemaObject** exposes extra parameters. Here is the description
as found in RFC 4512 :
 
     4.1.2.  Attribute Types
 
@@ -51,7 +51,7 @@ The **AttributeType** **SchemaObject** e
              "distributedOperation" /  ; DSA-shared operational
              "dSAOperation"            ; DSA-specific operational
 
-The follwing methods have been added to cover the ones that are not already present in the
**SchemaObject** interface :
+The follwing methods have been added to cover ones not already present within the **SchemaObject**
interface :
 
 * getEquality() : returns the **MatchingRule** instance used to control the equality of the
**AttributeType**
 * getEqualityName() : returns the name of the EQUALITY **MatchingRule**.
@@ -78,4 +78,4 @@ The follwing methods have been added to
 * isUser() : tells if the **AttributeType** is a USER_APPLICATIONS attribute
 * isUserModifiable() : tells if the **AttributeType** is modifiable or not
 
-What is important to know is that an **AttributeType** may inherit some characteristics from
a **SUP** **AttributeType**. For instance, the **Syntax**, **MatchingRules**, etc. In any
case, if you don't define the specific characteristics for a give **AttributeType**, they
will be inherited from its parent, if there is one.
+What is important to know is that an **AttributeType** may inherit some characteristics from
a **SUP** **AttributeType**. For example, the **Syntax**, **MatchingRules**, etc. In any case,
if you don't define the specific characteristics for a given **AttributeType**, they'll be
inherited from its parent -- if there is one.

Modified: directory/site/trunk/content/api/user-guide/4.2.1.2-object-classes.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/4.2.1.2-object-classes.mdtext?rev=1776795&r1=1776794&r2=1776795&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/4.2.1.2-object-classes.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4.2.1.2-object-classes.mdtext Sat Dec 31 16:42:10
2016
@@ -24,7 +24,7 @@ Notice: Licensed to the Apache Software
 
 # 4.2.1.2 - ObjectClasses
 
-The **ObjectClass** is representing thelist of mandatory and optional **AttributeType**s
+The **ObjectClass** represents the list of mandatory and optional **AttributeType**s
 
 Here is the description as found in RFC 4512 :
 
@@ -43,7 +43,7 @@ Here is the description as found in RFC
 
 Each **ObjectClass** as a type (ABSTRACT, STRUCTURAL or AUXILIARY) and may inherit from another
**ObjectClass**
 
-The important part of the **ObjectClass** is the **AttributeType** definition : not only
it lists all the **AttributeTypes** defined in itself, but also all the inherited ones. Note
that you may have an optionnal **AttributeType** defined in a parent, which is made mandatory.
+The important part of the **ObjectClass** is the **AttributeType** definition : not only
does it list all of the **AttributeTypes** defined in the list itself, but it also contains
the inherited attribute types. Note that you may have an optional **AttributeType** defined
in a parent, which is made mandatory.
 
 The available methods are :
 

Modified: directory/site/trunk/content/api/user-guide/4.2.1.3-syntaxes.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/4.2.1.3-syntaxes.mdtext?rev=1776795&r1=1776794&r2=1776795&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/4.2.1.3-syntaxes.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4.2.1.3-syntaxes.mdtext Sat Dec 31 16:42:10
2016
@@ -24,7 +24,7 @@ Notice: Licensed to the Apache Software
 
 # 4.2.1.3 - Syntaxes
 
-The **LdapSyntax** class implements the LDAP **Syntax**s schema objects. A **Syntax** defines
a constraints applied to the **AttributeType** value. Here is the TFC description of a **Syntax**
:
+The **LdapSyntax** class implements the LDAP **Syntax**s schema objects. A **Syntax** defines
constraints applied to the **AttributeType** value. Here is the RFC description of a **Syntax**
:
 
      SyntaxDescription = LPAREN WSP
          numericoid                 ; object identifier
@@ -37,7 +37,7 @@ In order to enforce a **Syntax**, the **
 
 ## Methods
 
-The two important methods you might use are :
+The are the two most important methods that you might need:
 
 * getSyntaxChecker() : retreive the associated class that is used to check a syntax
 * isHumanReadable() : tells if the AttributeType is a String or a byte[]

Modified: directory/site/trunk/content/api/user-guide/4.2.1.4-matching-rules.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/4.2.1.4-matching-rules.mdtext?rev=1776795&r1=1776794&r2=1776795&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/4.2.1.4-matching-rules.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4.2.1.4-matching-rules.mdtext Sat Dec 31 16:42:10
2016
@@ -24,22 +24,22 @@ Notice: Licensed to the Apache Software
 
 # 4.2.1.4 - MatchingRules
 
-A **MatchingRule** is used when processing a search **Filter** evaluation, or a **Compare**
or **Modify** operation. An **AttributeType** can define up to 3 types of **MatchingRule**
:
+A **MatchingRule** is used when processing search requests using **Filter**s, or a **Compare**
or during **Modify** operations. An **AttributeType** defines up to 3 types of **MatchingRule**s:
 
 * EQUALITY : for comparisons for equality
 * ORDERING : for comparisons involving the <= or >= operators
 * SUBSTR : for comparisons involving substrings, like '*xyz' or 'x*z'
 
-There are a few extra parameter that are defined in the **MatchingRule** class :
+There are a few extra parameters that are defined in the **MatchingRule** class:
 
 * getSyntax() : gets the **Syntax** instance associated with the **MatchingRule**
 * getSyntaxOid() : gets the **Syntax** OID associated with the **MatchingRule**
 
-We also have 2 specific methods that are used to compare or normalize a value :
+We also have 2 specific methods that are used to compare or normalize a value:
 
 * getLdapComparator() : gets the **LdapComparator** to use to compare 2 values
 * getNormalizer() : gets the **Normalizer** used to normalize a value
 
-Those are convenient methods, specifically when you will need to compare two values.
+Those are convenient methods, specifically when you need to compare two values.
 
 A **MatchingRule** instance is associated with a **LdapSyntax** and a **Normalizer** because
it may need to get information about the attribute value check and normalization. It also
contains a reference to the associated **LdapComparator**.

Modified: directory/site/trunk/content/api/user-guide/4.2.1.8-name-forms.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/api/user-guide/4.2.1.8-name-forms.mdtext?rev=1776795&r1=1776794&r2=1776795&view=diff
==============================================================================
--- directory/site/trunk/content/api/user-guide/4.2.1.8-name-forms.mdtext (original)
+++ directory/site/trunk/content/api/user-guide/4.2.1.8-name-forms.mdtext Sat Dec 31 16:42:10
2016
@@ -3,7 +3,7 @@ NavPrev: 4.2.1.7-matching-rule-use.html
 NavPrevText: 4.2.1.7 - Matching Rule Uses
 NavUp: 4.2.1-schema-objects.html
 NavUpText: 4.2.1 - Schema Objects
-NavNext: 4.2.1.9-apacheds-schema-eleemnts.html
+NavNext: 4.2.1.9-apacheds-schema-elements.html
 NavNextText: 4.2.1.9 - ApacheDS Schema Elements
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
@@ -24,4 +24,4 @@ Notice: Licensed to the Apache Software
 
 # 4.2.1.8 - NameForms
 
-Not yet supported...
\ No newline at end of file
+Not yet supported...



Mime
View raw message