-
Bug
-
Resolution: Unresolved
-
P4
-
11, 23
-
None
-
generic
-
generic
The default values of the JNDI provider environment properties listed in jndiprovider.properties file contain non-existing classes.
The following classes are not shipped with JDK and can cause com.sun.naming.internal.ResourceManager.getFactories fail to load the classes mentioned in the properties file:
com.sun.jndi.ldap.ctl.ResponseControlFactory
com.sun.jndi.ldap.obj.AttrsToCorba
com.sun.jndi.ldap.obj.MarshalledToObject
com.sun.jndi.ldap.obj.RemoteToAttrs
com.sun.jndi.ldap.obj.CorbaToAttrs
The use cases of java.naming.factory.object, java.naming.factory.control and java.naming.factory.state environment properties needs to be investigated to confirm that the above class references can be removed from jndiprovider.properties file, or maybe the whole properties file can be removed.
The properties file path in JDK repository:
src/java.naming/share/classes/com/sun/jndi/ldap/jndiprovider.properties
The following classes are not shipped with JDK and can cause com.sun.naming.internal.ResourceManager.getFactories fail to load the classes mentioned in the properties file:
com.sun.jndi.ldap.ctl.ResponseControlFactory
com.sun.jndi.ldap.obj.AttrsToCorba
com.sun.jndi.ldap.obj.MarshalledToObject
com.sun.jndi.ldap.obj.RemoteToAttrs
com.sun.jndi.ldap.obj.CorbaToAttrs
The use cases of java.naming.factory.object, java.naming.factory.control and java.naming.factory.state environment properties needs to be investigated to confirm that the above class references can be removed from jndiprovider.properties file, or maybe the whole properties file can be removed.
The properties file path in JDK repository:
src/java.naming/share/classes/com/sun/jndi/ldap/jndiprovider.properties