| Summary: | PartInitException could be more specific in ViewFactory.createView | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kevin McGuire <Kevin_McGuire> |
| Component: | UI | Assignee: | Eric Moffatt <emoffatt> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | remy.suen |
| Version: | 3.4 | ||
| Target Milestone: | 3.5 | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | |||
It could instead say: "Could not find view ID: <viewId>" I'll take this one...it's a subset of the 'failures' should be more graceful defect which I hope to take a cut at in 3.5. Marking as a DUP of the defect we're using to track dynamic plugin issues... *** This bug has been marked as a duplicate of bug 218197 *** |
ViewFactory.createView throws PartInitException. The resulting message is: "Could not create view: <viewId>" The failure is actually because the id is not in the view registry: IViewDescriptor desc = viewReg.find(id); // ensure that the view id is valid if (desc == null) { throw new PartInitException(NLS.bind(WorkbenchMessages.ViewFactory_couldNotCreate, id )); } It would be helpful if the message was more specific as PartInitException can be thrown for a number of reasons.