JDK-4343723 : Beans.instantiate() does not preserve nested exception
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.beans
  • Affected Version: 1.2.2,1.4.1,1.4.2
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2000-06-06
  • Updated: 2009-07-10
  • Resolved: 2003-04-02
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
5.0 tigerFixed
Related Reports
Duplicate :  
Relates :  
Description

Name: skT45625			Date: 06/06/2000

java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)


The following code in Beans.instantiate()

} catch (Exception ex) {
   // We have to remap the exception to one in our signature.
   // But we pass extra information in the detail message.
   throw new ClassNotFoundException("" + cl + " : " + ex);
}

should read (note ", ex" added at end) as below

...new ClassNotFoundException("" + cl + " : " + ex, ex);

so that the location (e.g., line number) of the nested error is
preserved for later stack dumps.
(Review ID: 105784) 
======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b04
14-06-2004

PUBLIC COMMENTS .
10-06-2004

EVALUATION Not sure what the user is requesting. I think the developer wants a way of preserving the stacktrace when an exception is rethrown. However, the fix that is suggested is syntactically incorrect and I'm unclear on the nature of the fix. I'm not going to fix it. mark.davidson@Eng 2000-06-21 I'm sorry. I misread the bug the first time. This is an easy fix. I'll commit to 1.5. ###@###.### 2003-03-19
21-06-2000