Project

General

Profile

bug #8843

Revise term caching

Added by Andreas Kohlbecker 5 months ago. Updated 5 months ago.

Status:
New
Priority:
New
Assignee:
Category:
taxeditor
Target version:
Start date:
02/05/2020
Due date:
% Done:

0%

Severity:
normal
Found in Version:

Description

The actual mechanisms of the term caching in the teaxeditor is unclear and undocumented. Several parallel classes and concepts exist whereas it is not clear if these are complementary or redundant.

The documentation in TaxonomicEditorDevelopersGuide only mentions the term caching in CachingHttpInvokerProxyFactoryBean.handleTermRequest(RemoteInvocation invocation, MethodInvocation originalInvocation) but there is also the TermStore class which is supposed to load important terms on application startup.

Open questions and Problems:

  1. Why does CachingHttpInvokerProxyFactoryBean (formerly CdmServiceRequestExecutor, see #8842) distinguish terms from other cdm entities where CdmTransientEntityCacher is caching term internally anyway in the CdmTransientEntityCacher.permanentCache? Some terms would end up being cached in the permanentCache others in the RemoteInvocationTermCacher.termTypeMap
  2. Is the TermStore the fist mechanism mentioned in TaxonomicEditorDevelopersGuide#Term-Loading, or is this something different?

TODO

  1. improve type level documentation
  2. improve and update the TaxonomicEditorDevelopersGuide

Related issues

Related to Edit - bug #8842: CdmServiceRequestExecutor is not stateleass and neither thread save nor access synchronized Resolved 02/04/2020

History

#1 Updated by Andreas Kohlbecker 5 months ago

  • Description updated (diff)

#2 Updated by Andreas Kohlbecker 5 months ago

  • Related to bug #8842: CdmServiceRequestExecutor is not stateleass and neither thread save nor access synchronized added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)