JDK-4487432 : NamingException needs to be integrated with new Throwable's getCause
  • Type: Bug
  • Component: core-libs
  • Sub-Component: javax.naming
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_2.6
  • CPU: sparc
  • Submitted: 2001-08-02
  • Updated: 2003-04-12
  • Resolved: 2002-08-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.2 mantisFixed
Related Reports
Relates :  
Relates :  
Description
getCause() and initCause() need to be modified to track the same "cause"
as getRootCause() and setRootCause().  Also, printStackTrace() needs to be modified so that invocations behave consistently with other exceptions in 
the JDK that have nested exceptions.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis mantis-b02 FIXED IN: mantis mantis-b02 INTEGRATED IN: mantis mantis-b02
02-09-2004

PUBLIC COMMENTS -
02-09-2004

EVALUATION ###@###.### 2002-01-22 Use Throwable.getCause() to implement NamingException.getRootCause(). ###@###.### 2002-04-23 Actually, use NamingException.getRootCause() to implement Throwable.getCause(), and NamingException.setRootCause() to implement Throwable.initCause(). ###@###.### 2002-07-22 In addition to the above, delete the overrides for printStackTrace(). Throwable.printStackTrace() has done the right thing since 1.4, so there's no longer a reason to bypass it.
22-07-2002