Details
-
Bug
-
Resolution: Workaround exists
-
Neutral
-
None
-
None
-
None
-
None
-
tomcat-8.5.5, java8, ubuntu 16.04. Connected molules: sitemesh, advancedcache and memcached implementation.
Description
I have a component with defined fragmentDefinition. I request the magnolia component on the client side from the external system, as shown in https://documentation.magnolia-cms.com/display/DOCS/Rendering+content in the "Direct component rendering" section.
As a result, there are next problems:
1) When URL is requested, for example http://local.mvideo.ru:8080/magnoliaPublic/travel/main/0, the key with uri=/magnoliaPublic/travel/main/0 will be stored in the cache, request marked as CachePolicyResult.useCache and then dynamic fragment will be called, the same key(/magnoliaPublic/travel/main/0) is saved in the cache. Thus, double saving of data with the same key in the cache.
2) Also, when URL is requested, the page or component is rendered ftl and put data in the browsercache, then the component with fragmentDefinition is rendered ftl again. As a result, there are two calls to render the same component. It is the overhead. You must avoid double-calling the same data.