Project

General

Profile

Actions

bug #9627

open

Handle updated objects correctly in monitored operations in taxeditor

Added by Andreas Müller almost 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
New
Category:
taxeditor
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:

Description

Currently in AbstractUtility.executeMoniteredOperation()

Set<Taxon> taxaToUpdate = getTaxaToUpdate(firstRemotingMonitor);
updateNameEditors(taxaToUpdate);

is called which updates only name editors and only if the result contains taxonBase. This is both not correct. All editors should be updated if datat stored in them is involved. Also not only taxa should be checked but any data that might be part of the session of the corresponding editor.

Also other long running tasks calling ProgressMonitorClientManager.pollMonitor should be handled the same way probably.


Related issues

Related to EDIT - task #9628: Improve update result handling for monitored operationsNewKatja Luther

Actions
Copied from EDIT - bug #6359: Remaining issues secundum for subtreesClosedAndreas Müller

Actions
Actions #1

Updated by Andreas Müller almost 3 years ago

  • Copied from bug #6359: Remaining issues secundum for subtrees added
Actions #2

Updated by Andreas Müller almost 3 years ago

  • Related to task #9628: Improve update result handling for monitored operations added
Actions #3

Updated by Andreas Müller almost 3 years ago

  • Target version changed from Release 5.25 to Release 5.45
Actions

Also available in: Atom PDF