Project

General

Profile

Actions

bug #7399

closed

Adding taxon nodes to working sets leads to MultipleRepresentationException

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

Status:
Closed
Priority:
New
Assignee:
Patrick Plitzner
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:

100%

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

Description

Steps to reproduce:

  1. Create a working set
  2. Add a taxon node to it
  3. Save
  4. Close WS editor and Re-Connect
  5. Open working set in WS editor
  6. Add another node from the same classification -> exception
Actions #1

Updated by Patrick Plitzner almost 5 years ago

  • Status changed from New to Feedback
  • Assignee changed from Patrick Plitzner to Andreas Müller

For testing purpose I removed @Cascade({CascadeType.SAVE_UPDATE,CascadeType.MERGE}) from Set<TaxonNode> taxonSubtreeFilter in the WorkingSet model class and the problem was fixed.
Is cascading necessary here?

Actions #2

Updated by Andreas Müller almost 5 years ago

  • Assignee changed from Andreas Müller to Patrick Plitzner

we may think about removing the Cascade as it is probably not necessary. However, a multiple-representations exception is usually a hint that something is not done correctly somewhere so I would prefer to first understand why the problem occurs and fix it and then remove Cascade.

Actions #3

Updated by Andreas Müller almost 5 years ago

  • Target version changed from Unassigned CDM tickets to Release 5.0
Actions #4

Updated by Patrick Plitzner over 4 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 50
Actions #5

Updated by Patrick Plitzner over 4 years ago

  • Assignee changed from Patrick Plitzner to Andreas Müller
  • % Done changed from 50 to 0
Actions #6

Updated by Patrick Plitzner over 4 years ago

  • % Done changed from 0 to 50
Actions #7

Updated by Andreas Müller over 4 years ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Andreas Müller to Patrick Plitzner

As you have detected the issue and know the background you can probably best decide if you think this ticket is fixed.

Feel free to close when you think the issue is fully fixed.

Actions #8

Updated by Patrick Plitzner over 4 years ago

  • Status changed from Feedback to Closed
  • % Done changed from 50 to 100
Actions

Also available in: Atom PDF