Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358237 - Save failed
Summary: Save failed
Status: RESOLVED FIXED
Alias: None
Product: Ecoretools
Classification: Modeling
Component: General (show other bugs)
Version: 1.0   Edit
Hardware: PC Windows 7
: P3 normal
Target Milestone: 2.0.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-20 08:47 EDT by Nicolas Bros CLA
Modified: 2014-04-29 12:14 EDT (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 Nicolas Bros CLA 2011-09-20 08:47:01 EDT 
When I tried to save, I got a "save failed" message an nothing was saved, resulting in lost work. See the attached stacktrace.
Comment 1 Nicolas Bros CLA 2011-09-20 08:50:12 EDT 
When I tried to reopen the editor after the failed save, it failed too:

Unable to create editor ID org.eclipse.emf.ecoretools.diagram.part.EcoreDiagramEditorID: An exception was thrown during initialization

Stacktrace:
java.lang.ClassCastException
(yes, this is all I see in the error log)
Comment 2 Nicolas Bros CLA 2011-09-20 08:56:24 EDT 
In fact, the EcoreTools editor also broke opening of my model file. When I try to open my model.ecore, I now also get:
Unable to create editor ID org.eclipse.emf.ecore.presentation.EcoreEditorID: An unexpected exception was thrown.
Stacktrace:
java.lang.ClassCastException


After restarting Eclipse, the ecore file opens again in the ecore editor. So I suspect the EcoreTools editor must have messed with runtime information, such as the Ecore metamodel in the EPackage registry.
Comment 3 Cedric Brun CLA 2014-01-06 08:43:12 EST 
I can't reproduce that using EcoreTools 2.0, it should be pretty robust in this regard now that it is based on Sirius.