Summary: | Should handle JavaModelExceptions that contains CoreException more gracefully | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Jerome Lanneluc <jerome_lanneluc> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 M6 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Jerome Lanneluc
2002-04-11 06:32:20 EDT
I agree that the wrappered information should not be lost. However, this should be done by the JavaModelException transparently, i.e., when a CoreException is wrappered then the getStatus call should be forwarded by the JavaModelException to the wrappered CoreException. This is also the approach taken in Throwable in JDK 1.4 were there is support for exception wrappering in Throwable directly. Moving back to JDT core. When a JavaModelException wraps a CoreException, the status of the CoreException is now remembered instead of creating a JavaModelStatus. |