java.lang.Object javax.naming.ldap.ControlFactoryThis abstract class represents a factory for creating LDAPv3 controls. LDAPv3 controls are defined in RFC 2251.
When a service provider receives a response control, it uses control factories to return the specific/appropriate control class implementation.
|Method from javax.naming.ldap.ControlFactory Summary:|
|Methods from java.lang.Object:|
|clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait|
|Method from javax.naming.ldap.ControlFactory Detail:|
abstract public Control getControlInstance(Control ctl) throws NamingException
The factory is used by the service provider to return controls that it reads from the LDAP protocol as specialized control classes. Without this mechanism, the provider would be returning controls that only contained data in BER encoded format.
Typically, ctl is a "basic" control containing BER encoded data. The factory is used to create a specialized control implementation, usually by decoding the BER encoded data, that provides methods to access that data in a type-safe and friendly manner.
For example, a factory might use the BER encoded data in basic control and return an instance of a VirtualListReplyControl.
If this factory cannot create a control using the argument supplied, it should return null. A factory should only throw an exception if it is sure that it is the only intended factory and that no other control factories should be tried. This might happen, for example, if the BER data in the control does not match what is expected of a control with the given OID. Since this method throws NamingException, any other internally generated exception that should be propagated must be wrapped inside a NamingException.
public static Control getControlInstance(Control ctl, Context ctx, Hashtable<?, ?> env) throws NamingException
The following rule is used to create the control:
Note that a control factory must be public and must have a public constructor that accepts no arguments.