Bug 106500 - Support nexted exceptions in weaver/compiler
Summary: Support nexted exceptions in weaver/compiler
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: DEVELOPMENT   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 1.5.0 M4   Edit
Assignee: Adrian Colyer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-09 11:40 EDT by Matthew Webster CLA
Modified: 2005-10-15 08:05 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Webster CLA 2005-08-09 11:40:10 EDT 
There are a number of places in the weaver where we catch exceptions e.g. 
IOException and rethrow an application-specific exceptions e.g. BCException. 
Unfortunately because we need to continue to support JDK 1.3 we cannot nest 
the exceptions and so the stack trace is lost. We should define a root 
exception for the weaver and add a constructor to allow nesting: we can use 
RemoteException as a model.
Comment 1 Adrian Colyer CLA 2005-08-26 11:43:19 EDT 
will assist with bug fixing in run-up to 1.5.0 final
Comment 2 Adrian Colyer CLA 2005-10-15 08:05:50 EDT 
I fixed this just before I left IBM. BCException can take a cause exception and does so in the appropriate 
places.