Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354836 - Clean up and refactor the runtime's exceptions and exception handling
Summary: Clean up and refactor the runtime's exceptions and exception handling
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: EDT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Matt Heitz CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-16 10:20 EDT by Matt Heitz CLA
Modified: 2017-02-23 14:16 EST (History)
1 user (show)

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 Matt Heitz CLA 2011-08-16 10:20:18 EDT 
* delete EglException (it's replaced in EDT by AnyException)
* rename EglThrowable to ControlFlow (a better name)
* rename FatalException to FatalProblem (a better name)
* the generated catch block for AnyExceptions should re-throw FatalProblems and ControlFlows
* use/remove/update the many exception-related methods in JavartUtil (especially see the noExceptionHandlers method)
Comment 1 Matt Heitz CLA 2011-08-16 10:23:59 EDT 
* merge JavartException into AnyException because we don't need both of them
Comment 2 Matt Heitz CLA 2011-08-16 18:37:25 EDT 
Done.
Comment 3 Matt Heitz CLA 2011-08-16 18:38:38 EDT 
I generated all of the exceptions (and enumerations), and sucked them into the runtime project.  This means their Java packages will now match their EGL packages, so a few other gen/runtime changes were necessary.
Comment 4 Lisa Lasher CLA 2011-08-26 18:00:23 EDT 
changing to Enhancement, as this isn't really a defect.
Comment 5 Matt Heitz CLA 2011-09-08 13:50:51 EDT 
Closing.