Project

General

Profile

Actions

bug #8194

closed

LazyInitializationException (LIE) on deleting the nomenclatural referenz (Section) of a Name

Added by Andreas Kohlbecker about 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Highest
Category:
cdm-vaadin
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
critical
Found in Version:
Tags:

Description

Habe die Section des eines Namens die als nomenklatorische Referenz gesetzt war löschen wollen:

http://phycobank.org/101145

und bekam im Reference Editor:

org.hibernate.LazyInitializationException: could not initialize proxy - no Session
               at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:148)
               at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:266)
               at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:68)
               at eu.etaxonomy.cdm.model.agent.TeamOrPersonBase_$$_jvst12a_62.getNomenclaturalTitle(TeamOrPersonBase_$$_jvst12a_62.java)
               at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getAuthorAndExAuthor(TaxonNameDefaultCacheStrategy.java:254)
               at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getNonCacheAuthorshipCache(TaxonNameDefaultCacheStrategy.java:196)
               at eu.etaxonomy.cdm.strategy.cache.name.TaxonNameDefaultCacheStrategy.getAuthorshipCache(TaxonNameDefaultCacheStrategy.java:170)
               at eu.etaxonomy.cdm.model.name.TaxonName.updateAuthorshipCache(TaxonName.java:3595)
               at eu.etaxonomy.cdm.model.name.TaxonName.getTitleCache(TaxonName.java:1498)
               at eu.etaxonomy.cdm.service.CdmStore.lambda$handleDeleteresultInError$1(CdmStore.java:205)
               at java.lang.Iterable.forEach(Iterable.java:75)
               at eu.etaxonomy.cdm.service.CdmStore.handleDeleteresultInError(CdmStore.java:202)
               at eu.etaxonomy.cdm.service.CdmStore.deleteBean(CdmStore.java:170)
               at eu.etaxonomy.vaadin.mvp.CdmEditorPresenterBase.deleteBean(CdmEditorPresenterBase.java:297)
               at eu.etaxonomy.vaadin.mvp.AbstractEditorPresenter.onEditorDeleteEvent(AbstractEditorPresenter.java:118)

Files

picture144-1.png (49 KB) picture144-1.png Andreas Kohlbecker, 03/22/2019 03:17 PM

Related issues

Related to EDIT - feature request #8204: RegistrationWorkingsetEditor shows list of unused sections and allows for delting themNewAndreas Kohlbecker

Actions
Actions #1

Updated by Andreas Kohlbecker about 5 years ago

Initializing the authorteam of the inReferences of the references loaded by the combobox should solve the problem.

Actions #2

Updated by Andreas Kohlbecker about 5 years ago

  • Subject changed from LazyInitializationException (LIE) on deleting the nomenklatorical referenz (Section) of a Name to LazyInitializationException (LIE) on deleting the nomenclatural referenz (Section) of a Name
Actions #3

Updated by Andreas Kohlbecker about 5 years ago

Actions #4

Updated by Andreas Kohlbecker about 5 years ago

  • Description updated (diff)
Actions #5

Updated by Andreas Kohlbecker about 5 years ago

  • Related to feature request #8204: RegistrationWorkingsetEditor shows list of unused sections and allows for delting them added
Actions #6

Updated by Andreas Kohlbecker about 5 years ago

  • Status changed from New to Feedback
  • Assignee changed from Andreas Kohlbecker to Wolf-Henning Kusber

Even if the LazyInitializationException is avoided deletion of the section is impossible since it is still in use as nomenclaturalReference.

We have two options now to deal with this situation:

  1. hide the delete button in this situation and implement #8204
  2. show the delete button if the reference is a ISection having an inReference, once the delete button is pressed the nomencaltural reference is switched to the inReference and the delete operation is done afterwards

what do you think Henning?

Actions #7

Updated by Andreas Kohlbecker about 5 years ago

We agreed on :

  1. hide the delete button in this situation and implement #8204

Warning is sufficient, we don't need to hide the button.

Closing issue.

Actions #8

Updated by Andreas Kohlbecker about 5 years ago

  • Status changed from Feedback to Closed
  • Assignee changed from Wolf-Henning Kusber to Andreas Kohlbecker
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF