BPMN2Editor refresh behaviour [message #1085434] |
Mon, 12 August 2013 23:19 |
Marco Roque Messages: 16 Registered: July 2012 |
Junior Member |
|
|
Hi everyone,
I am trying to animate a BPMN2 diagram and for that i'm executing customFeature after customFeature, which sometimes results in the exception bellow.
From what i understand this happens because the diagram has its own Refresh Thread that is painting the diagram from time to time, sometimes at the same time as i am executing a customFeature. Am i wrong?
Or, on the other hand, is the refresh a result of the execution of a customFeature which leaves the diagram in a dirty state?
Is there any way to turn off the automatic refresh and be my code to control the refresh of the diagram?
sorry for the questioning...
Many thanks in advance.
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextEntry(Unknown Source)
at java.util.HashMap$KeyIterator.next(Unknown Source)
at org.eclipse.graphiti.ui.internal.editor.DiagramRefreshJob.runInUIThread(DiagramRefreshJob.java:104)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4144)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1053)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:942)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
Regards
Marco Roque
[Updated on: Mon, 12 August 2013 23:23] Report message to a moderator
|
|
|
Re: BPMN2Editor refresh behaviour [message #1085449 is a reply to message #1085434] |
Mon, 12 August 2013 23:53 |
|
Hi Marco,
This is probably a question for the Graphiti group, because the BPMN2 editor does not really control the diagram refresh. You could try overriding BPMN2Editor.refresh() and controlling the refresh that way, but I'm not sure if that will work.
Bob
|
|
|
|
|
Re: BPMN2Editor refresh behaviour [message #1087416 is a reply to message #1087240] |
Thu, 15 August 2013 15:57 |
|
Sorry, this is not possible at this time. The BPMN2Editor is actually referenced (indirectly) by the BPMN2MultiPageEditor, so that class would have to be changed to use a delegate pattern so you could plug in your own implementation.
Again, feel free to file an enhancement request
|
|
|
Powered by
FUDForum. Page generated in 0.02944 seconds