Taxonnode parent merge cascade leads to non-transactional behavior
If a taxon node is changed and saved the update result also contains its parent and also grandparents up to the classification. This can be seen in the session view of the TaxEditor When saving again all these objects are also merged.
This is not only a performance issue for deeper classifications but it also leads to a situation that if the parent was edited and saved in the meanwhile this editing gets lost because the parent state of the child is saved afterwards.
This behavior can be reproduced by:
- Open parent and child
- Change child (e.g. publish flag) and save
- Change parent (e.g. publish flag) and save
- Change child again and save
Reopen parent => it has the state from before the change
This is critical.
NOTE: Before closing: think about removing SaveOrUpdateEntityListener. It is currently not used anymore.
Updated by Andreas Müller over 2 years ago
- Status changed from New to Resolved
- Assignee changed from Andreas Müller to Katja Luther
- Priority changed from New to Highest
- % Done changed from 0 to 50
This needs intensive reviewing as I removed cascading taxon node to parent.
I tested already that the problem itself is solved. I tested the steps from the description and now the new state remains after the child was saved.