Generated by
JDiff

javax.naming.ldap Documentation Differences

This file contains all the changes in documentation in the package javax.naming.ldap as colored differences. Deletions are shown like this, and additions are shown like this.
If no deletions or additions are shown in an entry, the HTML tags will be what has changed. The new HTML tags are shown in the differences. If no documentation existed, and then some was added in a later version, this change is noted in the appropriate class pages of differences, but the change is not shown on this page. Only changes in existing text are shown here. Similarly, documentation which was inherited from another class or interface is not shown here.
Note that an HTML error in the new documentation may cause the display of other documentation changes to be presented incorrectly. For instance, failure to close a <code> tag will cause all subsequent paragraphs to be displayed differently.

Class InitialLdapContext

This class is the starting context for performing LDAPv3-style extended operations and controls.

See javax.naming.InitialContext and javax.naming.InitialDirContext for details on synchronization and the policy for how an initial context is created.

Request Controls

When you create an initial context (InitialLdapContext) you can specify a list of request controls. These controls will be used as the request controls for any implicit LDAP "bind" operation performed by the context or contexts derived from the context. These are called connection request controls. Use getConnectControls() to get a context's connection request controls.

The request controls supplied to the initial context constructor are not used as the context request controls for subsequent context operations such as searches and lookups. Context request controls are set and updated by using setRequestControls().

As shown there can be two different sets of request controls associated with a context: connection request controls and context request controls. This is required for those applications needing to send critical controls that might not be applicable to both the context operation and any implicit LDAP "bind" operation. A typical user program would do the following:

 InitialLdapContext lctx = new InitialLdapContext(env critConnCtls); lctx.setRequestControls(critModCtls); lctx.modifyAttributes(name mods); Controls[] respCtls = lctx.getResponseControls(); 
It specifies first the critical controls for creating the initial context (critConnCtls) and then sets the context's request controls (critModCtls) for the context operation. If for some reason lctx needs to reconnect to the server it will use critConnCtls. See the LdapContext interface for more discussion about request controls.

Service provider implementors should read the "Service Provider" section in the LdapContext class description for implementation details. @author Rosanna Lee @author Scott Seligman @author Vincent Ryan @version 1.7 018 02/12/03/08 @see LdapContext @see javax.naming.InitialContext @see javax.naming.directory.InitialDirContext @see javax.naming.spi.NamingManager#setInitialContextFactoryBuilder @since 1.3