task #6745: Investigate how e4 model changes affect the cached application model in existing Taxeditor installation - EDIT - EDIT Project Management

Custom queries

5.33
cdm-dataportal (open)
last 7 days tickets
mine in current release
phycobank
phycobank-index-closed
phycobank-registration-closed
potentially missed issues
recently updated
Release3.7
Release3.8
Release4.0
Release4.1
Release4.10
Release4.11
Release4.12
Release4.13
Release4.14
Release4.16
Release4.2
Release4.3
Release4.4
Release4.5
Release4.6
Release4.7
Release4.8
Release4.9
Release4.9
Release5.0
Release5.1
Release5.10
Release5.11
Release5.12
Release5.13
Release5.14
Release5.15
Release5.16
Release5.17
Release5.18
Release5.19
Release5.2
Release5.20
Release5.21
Release5.22
Release5.23
Release5.24
Release5.25
Release5.26
Release5.27
Release5.28
Release5.29
Release5.3
Release5.30
Release5.31
Release5.32
Release5.33
Release5.34
Release5.35
Release5.36
Release5.37
Release5.38
Release5.39
Release5.4
Release5.40
Release5.41
Release5.5
Release5.6
Release5.7
Release5.8
Release5.9
Remoting-Versions
Taxeditor-UX (Platform Etablierung)

Actions

Copy link

task #6745

open

feature request #7431: [MASTER] remaining E4 migration issues

Investigate how e4 model changes affect the cached application model in existing Taxeditor installation

Added by Patrick Plitzner almost 7 years ago. Updated over 4 years ago.

Status:

New

Priority:

Highest

Assignee:

Katja Luther

Category:

taxeditor

Target version:

Reviewed Next Major Release

Start date:

Due date:

% Done:

Estimated time:

Severity:

normal

Tags:

eclipse4

Description

The application model of the Taxeditor is stored in {home}/.cdmLibrary/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi. This stores all parts, menu items, commands, etc.

While we are still migrating from e3 to e4 and make a lot of changes to the model there could be situation when after installing a new taxeditor (for developers: after git pull) new GUI objects do not show up because of the existing application model cache. Deleting the workbench.xmi file solves this problem (developers can also add -clearPersistedState to the program arguments in the launch configuration of the taxeditor.

We could think about about delivering an extra a batch file that starts the editor with the -clearPersistedState parameter in order to once reset the application model. Afterwards the editor could be started normally. Having this parameter set for every launch would always lead to a fresh application model i.e. none of the layout of the windows are opened editors would be restored.

We should look at the parameter apply in the org.eclipse.e4.workbench.model extension point which defines when a model fragment should be applied to the cached one.

====

This ticket may also include restore functionality of name editors (#7071)

====
a lot of eclipse initialization and lifecycle management is defined in plugin.xml of taxeditor.application

Files

picture298-1.png (75.9 KB) picture298-1.png

plugin.xml of taxeditor.application

Patrick Plitzner, 12/06/2019 12:16 PM

Related issues

Related to EDIT - task #6839: remove old workbench.xmi from .cdmlibrary

Rejected

Patrick Plitzner

Actions

Related to EDIT - feature request #7071: Reenable restore functionality

New

Katja Luther

Actions

Related to EDIT - feature request #7007: Migrate IMemento functionality

Rejected

Patrick Plitzner

Actions

Related to EDIT - bug #7997: Some editor windows do not open at the expected location

New

Katja Luther

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Patrick Plitzner almost 7 years ago

Tags set to eclipse4

Actions

Copy link

Updated by Andreas Müller almost 7 years ago

Ja, das ist ein wichtiges Thema. Insbesondere wenn man nightly häufig neuinstalliert, bekommt man beim ersten mal immer Probleme, weil er irgendwas öffnen will was irgendwo wohl mal geöffnet war, obwohl ich in der Zwischenzeit der Editor schon sehr häufig mit anderem Layout geschlossen habe.
Ich habe das noch nicht systematisch untersucht, aber sollten wir machen.

Actions

Copy link

Updated by Patrick Plitzner almost 7 years ago

Subject changed from Investigate how e4 model changes affect the cached application model in exisiting Taxeditor installation to Investigate how e4 model changes affect the cached application model in existing Taxeditor installation

Actions

Copy link

Updated by Andreas Müller almost 7 years ago

This is a general problem when working with >1 installations of the editor. We should try to store instance specific xmi files

Actions

Copy link

Updated by Patrick Plitzner almost 7 years ago

This article might help. Seems like you can programmatically store and load the application model.
http://www.vogella.com/tutorials/Eclipse4ModelPersistence/article.html

Actions

Copy link

Updated by Andreas Müller over 6 years ago

Related to task #6839: remove old workbench.xmi from .cdmlibrary added

Actions

Copy link

Updated by Patrick Plitzner over 6 years ago

After implementing #6847 the launch flag -clearPersistedState does not seem to work anymore. During development you have to manually delete the workbench.xmi in {workspace}/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/configuration

Maybe we can implement a switch for dev and release

Actions

Copy link

Updated by Patrick Plitzner over 6 years ago

Andreas:

"[Im Editor] der noch keine Verbindung zu einer DB hat, wird versucht, einen Nameeditor zu öffnen. Das scheint mir nicht sinnvoll. Es sollte erst nach öffnen der Verbindung passieren.

Wenn ich dann in den ausgegrauten Nameeditor klicke, bekomme ich zudem folgende NPE:

Ich habe das jetzt nochmal beobachtet. Es passiert immer, wenn man mehrere TaxEditor Instanzen parallel auf hat. Dann übernimmt er die Information von der bereits geöffneten Instanz. Da müssen wir uns noch was ausdenken."

login :

editor version : 4.11.0.201710181800

server :  ()

schema version :

os : Windows Server 2012 R2 6.3 amd64

java : 1.8.0_121

org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException)

                at org.eclipse.swt.SWT.error(SWT.java:4533)

                at org.eclipse.swt.SWT.error(SWT.java:4448)

                at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)

                at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4211)

                at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3827)

                at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)

                at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)

                at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)

                at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)

                at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)

                at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)

                at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)

                at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)

                at eu.etaxonomy.taxeditor.Application.start(Application.java:24)

                at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)

                at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)

                at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)

                at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)

                at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                at java.lang.reflect.Method.invoke(Method.java:498)

                at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)

                at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)

                at org.eclipse.equinox.launcher.Main.run(Main.java:1519)

Caused by: org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException

                at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:65)

                at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler$1.run(UIEventObjectSupplier.java:56)

                at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)

                at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)

                ... 23 more

Caused by: java.lang.NullPointerException

                at eu.etaxonomy.taxeditor.navigation.navigator.e4.TaxonNavigatorE4.updateCurrentTaxon(TaxonNavigatorE4.java:210)

                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

                at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                at java.lang.reflect.Method.invoke(Method.java:498)

                at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)

                ... 26 more

Actions

Copy link