EDIT

Explaining the already cleaned up code:

SetSelection in setFocus of TaxonNameEditorE4 is not necessary and yields to a second call of the same method (TaxonNameEditorE4.setFocus()).

The TermComboboxes are filled with the terms defined by the preferences or with the whole list of terms of the related type. For the reduced list, the find-call is done with a list of uuids and results alyways in a service call because in cacheTerms only listByTermType is handled.
Therefore the call of TermManager.getTerms(List, TermType) is changed in a way the terms are loaded from the TermStore and then filtered. Maybe this handling can still be improved in any way. But actually the DB calls are reduced and the correct terms are shown also after changing the preference.

The conversationHolder is a leftover from the times before remoting, so we removed it. Actually only a conversation mock was used.

Andreas Müller wrote in #note-7:

A critical issue: In AbstractCdmEditorPartE4 line 182 it is checked if (new) selection equals the previous selection. But this does not take into account that the selection may still change in an already added "sync.asyncExec(delaySelection);" call which is in the pipeline. So the latest focus/selection change may be swollowed by this check, however, the focus may be in the new position while the selection in the view-to-be-updated may later change to the selection previously selected and asynchronously called.
This is only the case when setting the focus back and forth between 2 different selections.

This should be fixed now with dad85080 and 20d52c89 . The result looks as far as now the focus and the selected data in the views seems to be always the same if one waits until the views have all loaded, even if you clicked before multiple times on different selections. However, it still needs intensive testing before being released.

Should we close this ticket and open a new one if we do further research on taxeditor sessions? I think there are a couple of issues that were fixed within this ticket or in related tickets opened during research.

Further issues can be handled in the more detailed tickets.