[MGNLPN-36] mainContentNode in AggregationState might be null in certain circumstances which might cause NPE in VariantResolverFilter Created: 19/Mar/14  Updated: 20/Mar/14  Resolved: 19/Mar/14

Status: Closed
Project: Magnolia Personalization
Component/s: Integration
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: Personalisation
Sprint: 5.3 Sprint 4

 Description   

mainContentNode in AggregationState might be null in certain circumstances which might cause NPE when checking for Mixin in the VariantResolverFilter (info.magnolia.jcr.util.NodeUtil#hasMixin).


Generated at Mon Feb 12 06:33:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.