bug #7399
closedAdding taxon nodes to working sets leads to MultipleRepresentationException
100%
Description
Steps to reproduce:
- Create a working set
- Add a taxon node to it
- Save
- Close WS editor and Re-Connect
- Open working set in WS editor
- Add another node from the same classification -> exception
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?
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.
Updated by Andreas Müller almost 5 years ago
- Target version changed from Unassigned CDM tickets to Release 5.0
Updated by Patrick Plitzner over 4 years ago
- Status changed from Feedback to Resolved
- % Done changed from 0 to 50
Applied in changeset taxeditor|a92e923ae40f1287477c73ef1a726b0e1325af35.
Updated by Patrick Plitzner over 4 years ago
- Assignee changed from Patrick Plitzner to Andreas Müller
- % Done changed from 50 to 0
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.
Updated by Patrick Plitzner over 4 years ago
- Status changed from Feedback to Closed
- % Done changed from 50 to 100