|
Quick Lists
|
|
Bug ID:
|
4794674
|
|
Votes
|
0
|
|
Synopsis
|
NamingException spec should conform to other chained exception legacies.
|
|
Category
|
jndi:doc
|
|
Reported Against
|
mantis-beta
|
|
Release Fixed
|
1.5(tiger)
|
|
State
|
10-Fix Delivered,
request for enhancement
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
4209652
,
4487432
|
|
Submit Date
|
17-DEC-2002
|
|
Description
|
A Chained Exception facility was added to the Throwable class in 1.4
(see RFE 4209652). This allows an exception to indicate that it was
thrown due to some other exception. By the time this facility was
added, a number of exception classes were using ad-hoc solutions to
the same problem. When 4209652 was integrated most of these ad-hoc
solutions were brought into line with the new generic facility but --
probably due to time constraints -- javax.naming.NamingException was not.
NamingException's behavior is already consistent with the treatment
given to other legacy classes, so only the javadoc needs to be updated
for consistency.
|
|
Work Around
|
N/A
|
|
Evaluation
|
xxxxx@xxxxx 2002-12-16
Update class javadoc to indicate that "root cause" and "cause" are one
and the same. Have legacy field and methods indicate that the general-purpose
exception chaining facility is preferred. Add javadoc to overridden methods
that copies the text from the superclass but omits bits that do not apply to
the subclass.
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |