Project

General

Profile

Actions

bug #8605

closed

ClassCastException in Feature editor when adding new Defined Term

Added by Andreas Kohlbecker over 4 years ago. Updated over 4 years ago.

Status:
Worksforme
Priority:
New
Category:
taxeditor
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:

Description

to reproduce

  • Use the database edit-WS I/caryophyllales_demo_01
  • open feature editor: Window > Terms > Feature
  • right click on the Feature Vocabulary -> new Defined Term
  • choose an existing term by clicking on it (e.g. Acknowlegement and edit the term by adding an abbreviation)
  • save the editor
  • right click on the term you just edited -> new Defined Term ==> BANG!

After this the problem always occurred when doing a right click on the term Acknolegement. Closing and reopening the Feature Editor did not help, is was necessary to close and reopen the Txeditor.

login : admin
editor version : 5.10.0
server : 160.45.63.230 (edit-WS I) / caryophyllales_demo_01
schema version : 5.8.2.0.20190815
os : Linux 5.0.0-31-generic amd64
java : 1.8.0_131
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ClassCastException: java.util.ArrayList cannot be cast to eu.etaxonomy.cdm.persistence.dto.TermDto)
    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:4536)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4154)
    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)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
Caused by: java.lang.ClassCastException: java.util.ArrayList cannot be cast to eu.etaxonomy.cdm.persistence.dto.TermDto
    at com.sun.proxy.$Proxy46.addNewTerm(Unknown Source)
    at eu.etaxonomy.taxeditor.editor.definedterm.operation.CreateDefinedTermOperation.execute(CreateDefinedTermOperation.java:55)
    at eu.etaxonomy.taxeditor.model.AbstractUtility.lambda$3(AbstractUtility.java:147)
    at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
    at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
    ... 24 more
Actions #1

Updated by Andreas Kohlbecker over 4 years ago

  • Subject changed from ClassCastException in Feature editor when addin new Defined Term to ClassCastException in Feature editor when adding new Defined Term
Actions #2

Updated by Andreas Kohlbecker over 4 years ago

  • Description updated (diff)
Actions #3

Updated by Andreas Müller over 4 years ago

  • Target version changed from Unassigned CDM tickets to Release 5.11

Personally I cannot reproduce this, but as it is a CCE we should fix it immediately.

PP+KL can you please decide who will fix it. TermEditor generally is PPs area but maybe its easy to fix anyway and PPs is at TDWG this week.

Actions #4

Updated by Patrick Plitzner over 4 years ago

  • Status changed from New to In Progress
  • Assignee changed from Katja Luther to Patrick Plitzner
Actions #5

Updated by Patrick Plitzner over 4 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from Patrick Plitzner to Andreas Kohlbecker

I could not reproduce this exception. But I am not sure what you mean with the 3rd step "choose an existing term (e.g. Acknolegement and edit the term by adding an abbreviation)". You cannot choose existing terms when adding new Defined Terms.
Were you using the Term Editor for features or the Term Tree Editor for features?

Actions #6

Updated by Andreas Kohlbecker over 4 years ago

  • Description updated (diff)

I extended the ticket descriptions to clarify what I did

Actions #7

Updated by Andreas Kohlbecker over 4 years ago

  • Assignee changed from Andreas Kohlbecker to Patrick Plitzner
Actions #8

Updated by Patrick Plitzner over 4 years ago

  • Assignee changed from Patrick Plitzner to Andreas Kohlbecker

I tested this with the latest nightly on the mentioned database but could not reproduce this behavior.

Actions #9

Updated by Andreas Kohlbecker over 4 years ago

  • Status changed from Feedback to Worksforme
  • Target version deleted (Release 5.11)

I can't reproduce this either, so it seems as if this has been fixed in the context of another task

Actions

Also available in: Atom PDF