Summary: | Different behavior handling Exception in Eclipse and outside | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Christophe Elek <celek> | ||||
Component: | Core | Assignee: | Olivier Thomann <Olivier_Thomann> | ||||
Status: | RESOLVED INVALID | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 3.0 | ||||||
Target Milestone: | 3.0 M5 | ||||||
Hardware: | PC | ||||||
OS: | Windows 2000 | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Christophe Elek
2003-10-23 16:47:10 EDT
Created attachment 6537 [details]
testcase
How did you compile your code? I guess it is related to the fact that .class no longer initialize the class. Before it did. Did you compile your code with two different versions of Eclipse or with javac? Hello Olivier Hum, good question Obviously I believe Eclipse 3.0 recompiled no ? I compiled with Eclipse 2.1 and exported Are you suggesting I compile and export with Eclipse 3.0 and an external JDK ? This has been changed between Eclipse 2.1 and Eclipse 3.0. It has nothing to do with the JDK that you are using. The problem is that you assumed that the class literal (DatabaseException.class) will initialize your class. This is not done anymore. See bug 37565. AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHh ! :) Ok to close? fine for me Close as INVALID. |