-
Bug
-
Resolution: Fixed
-
P4
-
1.0
-
1.1
-
generic
-
solaris_2.6
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2110006 | 1.0 | Unassigned | P4 | Closed | Won't Fix |
Noninherited instance variables in classes:
java.naming.CannotProceedException
java.naming.LinkException
java.naming.NamingException
java.naming.directory.AttributeModificationException
are not fully or consistently specified in documentation as to
their function, initial states in various constructors, or
translation in toString() operations. Note whenever a new constructor
is defined the initializers cannot be cut and pasted from the
old constructor API.
Documentation for nearly identical subclasses with identical functionality
have inconsistencies, such as java.naming.LinkLoopException or
java.naming.MalformedLinkException first constructor not saying
some fields are intialized to null,
yet this fact is stated in the identical parent class,
java.naming.LinkException
brian.preston@eng 1997-10-23
java.naming.CannotProceedException
java.naming.LinkException
java.naming.NamingException
java.naming.directory.AttributeModificationException
are not fully or consistently specified in documentation as to
their function, initial states in various constructors, or
translation in toString() operations. Note whenever a new constructor
is defined the initializers cannot be cut and pasted from the
old constructor API.
Documentation for nearly identical subclasses with identical functionality
have inconsistencies, such as java.naming.LinkLoopException or
java.naming.MalformedLinkException first constructor not saying
some fields are intialized to null,
yet this fact is stated in the identical parent class,
java.naming.LinkException
brian.preston@eng 1997-10-23
- backported by
-
JDK-2110006 instance variable init, consistent API and code for subclassing
-
- Closed
-