Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
While testing the CDE, found an instance where a custom resource was incorrectly configured (things were missing that it needed in the class path). The result of this was a silent failure to start the CDE editor, although an entry was noted in the Eclipse error log. This was because the missing class path caused a NoClassDefFound exception to be thrown, but nobody (except the top-most Eclipse UI code) caught it.
I think the right place for putting a try/catch is around the point in the CustomResourceFactory where it calls out to that resource's "initialize" method. If that throws an exception, it should be caught and wrapped with a new ResourceInitializationException, which says that the nested exception happened while trying to initialize the custom resource, and identifying the custom resource.