[MSITEMESH-64] DOC: Cache issues when component is both personalized and dynamic Created: 07/Feb/23  Updated: 23/Oct/23  Resolved: 27/Feb/23

Status: Closed
Project: SiteMesh
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Milan Divilek Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Relates
relates to MSITEMESH-59 cache does not work properly Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MSITEMESH-70 DOC: Cache issues when component is b... Sub-task Completed Martin Drápela  
MSITEMESH-71 DOC: Cache issues when component is b... Sub-task Completed Milan Divilek  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: DevX Bucket
Sprint: DevX 32
Story Points: 1
Team: DeveloperX
Work Started:

 Description   

These are two different mechanismus and is not easy to cache them together. We are not supporting it fully.

ComponentVariantInjectionListener is taking care about caching personalized compoments and FragmentInjectionListener about dynamic fragments, but it leads into injecting two sitemesh tags for one component(when component is p13n and dynamic).

MSITEMESH-59 disables injecting component variant tag when component is dynamic and personalized at the same time. Component then fully depends on tag injected for dynamic fragment, but it will correctly work only when TTL is set to 0. Any other setting can lead to unpredictable behaviour.


Generated at Mon Feb 12 10:57:26 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.