| Summary: | Could not open an existing diagram | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Modeling] Graphiti | Reporter: | Alexis Muller <Alexis.Muller> | ||||
| Component: | Core | Assignee: | Michael Wenz <michael.wenz> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | michael.wenz | ||||
| Version: | 0.7.0 | Flags: | michael.wenz:
iplog+
|
||||
| Target Milestone: | 0.7.0 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Hi Alexis, I have fixed this bug today in the CVS. Thanks for the bug report and the fix! -Michael Added version and target Part of 0.7.0 release |
Created attachment 174979 [details] Correction. Replace createFileURI by createPlatformResourceURI An exception is throw when opening an existing diagram in the workspace. For example : org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: java.io.FileNotFoundException: /fr.inria.mdfactory.chain.test/src/diagrams/new diagram.diagram (No such file or directory) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDemandLoadException(ResourceSetImpl.java:315) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:274) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:397) at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getEObject(ResourceSetImpl.java:216) at org.eclipse.graphiti.ui.editor.DiagramEditorInput.getEObject(DiagramEditorInput.java:610) at org.eclipse.graphiti.ui.editor.DiagramEditorInput.setEditorEditingDomain(DiagramEditorInput.java:512) at org.eclipse.graphiti.ui.editor.DiagramEditorInput.<init>(DiagramEditorInput.java:239) at org.eclipse.graphiti.ui.editor.DiagramEditorFactory.createEditorInput(DiagramEditorFactory.java:68) at org.eclipse.graphiti.ui.internal.editor.DiagramEditorInternal.init(DiagramEditorInternal.java:1055) at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:798) ... A possible correction, in the attached patch. PS : Very promising project ! Many thanks.