[MAGNOLIA-5524] CheckAndModifyPropertyValueTask throws NPE instead of logging an error Created: 04/Dec/13  Updated: 05/Dec/13  Resolved: 04/Dec/13

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.5.14, 5.2
Fix Version/s: 4.5.15, 5.2.1

Type: Bug Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-5182 CheckAndModifyPropertyValueTask shoul... Closed
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

 Description   

This is due to usage of
SessionUtil.getNode(workspaceName, nodePath) instead of jcrSession.getNode(nodePath). The former will return null in case of a PathNotFoundException leading to NPE in the subsequent method call, whereas the latter would throw an exception which is caught and logged to the user


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