bug #7842
TaxonNamePopEditor: adding new name as replaced synonym to name with basionym causes NonUniqueObjectException
Status:
Closed
Priority:
Highest
Assignee:
Category:
cdm-vaadin
Target version:
Start date:
10/23/2018
Due date:
% Done:
100%
Severity:
major
Found in Version:
Description
This case is not expected to occur often in real live situations:
A name has a basionym with authorship A. Adding replaced synonym for which a new name is created whereas the replaced synonym shares the same authorteam A with the basionym leads to a NonUniqueObjectException when saving.
Adding an existing name with the the same authorteam A is not causing the exception
Caused by: org.hibernate.NonUniqueObjectException: A different object with the same identifier value was already associated with the session : [eu.etaxonomy.cdm.model.agent.Team#277] at org.hibernate.engine.internal.StatefulPersistenceContext.checkUniqueness(StatefulPersistenceContext.java:648) at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performUpdate(DefaultSaveOrUpdateEventListener.java:284) at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.entityIsDetached(DefaultSaveOrUpdateEventListener.java:227) at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:92) at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:73) at org.hibernate.internal.SessionImpl.fireSaveOrUpdate(SessionImpl.java:648) at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:640) at org.hibernate.engine.spi.CascadingActions$5.cascade(CascadingActions.java:218) at org.hibernate.engine.internal.Cascade.cascadeToOne(Cascade.java:398) at org.hibernate.engine.internal.Cascade.cascadeAssociation(Cascade.java:323) at org.hibernate.engine.internal.Cascade.cascadeProperty(Cascade.java:162) at org.hibernate.engine.internal.Cascade.cascade(Cascade.java:111) at org.hibernate.engine.internal.Cascade.cascade(Cascade.java:61) at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.cascadeOnUpdate(DefaultSaveOrUpdateEventListener.java:358) at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performUpdate(DefaultSaveOrUpdateEventListener.java:332) at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.entityIsDetached(DefaultSaveOrUpdateEventListener.java:227) at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:92) at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:73) at org.hibernate.internal.SessionImpl.fireSaveOrUpdate(SessionImpl.java:648) at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:640) at org.hibernate.engine.spi.CascadingActions$5.cascade(CascadingActions.java:218) at org.hibernate.engine.internal.Cascade.cascadeToOne(Cascade.java:398) at org.hibernate.engine.internal.Cascade.cascadeAssociation(Cascade.java:323) at org.hibernate.engine.internal.Cascade.cascadeProperty(Cascade.java:162)
Related issues
Associated revisions
fix #7842 reloading registration before adding blocking registrations
History
#1 Updated by Andreas Kohlbecker over 2 years ago
- File picture729-1.png View added
- Description updated (diff)
#2 Updated by Andreas Kohlbecker over 2 years ago
- Description updated (diff)
#3 Updated by Andreas Kohlbecker over 2 years ago
- Related to bug #7630: blocking registration relations get lost after saving adding a typedesignation to a newly created "typification only" registration added
#4 Updated by Andreas Kohlbecker over 2 years ago
This problem is caused by the code which creates the blocking registrations see #7630
#5 Updated by Andreas Kohlbecker over 2 years ago
- Target version changed from Release 5.5 to Release 5.4
#6 Updated by Andreas Kohlbecker over 2 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 50
Applied in changeset cdm-vaadin|c320e0fa87d07c13f3744f510c49504adf704f21.
#7 Updated by Andreas Kohlbecker over 2 years ago
- Status changed from Resolved to Closed
- % Done changed from 50 to 100
#8 Updated by Andreas Kohlbecker over 2 years ago
- Tags set to phycobank