[PAGES-1341] Avoid trigger JCR node.add() operations JCR delivery endpoint Created: 11/Sep/23  Updated: 23/Oct/23

Status: Open
Project: Magnolia pages module
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Dai Ha Assignee: Unassigned
Resolution: Unresolved 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 PAGES-1325 info.magnolia.rendering.spa.rest.v2.J... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
PAGES-1342 Implementation Sub-task To Do  
PAGES-1343 Review Sub-task To Do  
PAGES-1344 Pre-Integration QA Sub-task To Do  
PAGES-1345 QA Sub-task To Do  
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)
Epic Link: DevX Bucket
Team: DeveloperX

 Description   

Problem:

  • JcrDeliveryEndpoint is only meant to read node, trigger modification JCR apis will cause operation denied error.

PAGES-1325 is one example.

Alternative:

  • For autogenerated node -> create a node placeholders
  • For inheritance node -> refer to parents node instead of adding the same inherited node to the current node.

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