[MGNLUI-3874] Firing ContentChangeEvent on the root node logs warning Created: 04/May/16  Updated: 15/Jun/16  Resolved: 15/Jun/16

Status: Closed
Project: Magnolia UI
Component/s: framework
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Roman Kovařík
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-3889 ExpandNodeAction is flooding log with... Closed
relates to PAGES-61 DefaultValue does not work for page p... Closed
duplicate
is duplicated by MGNLUI-3914 HierarchicalJcrContainer#getParent(Ob... 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)
Date of First Response:

 Description   

We can go to the next dialog when chaining dialogs and the related item doesn't have to be saved into JCR yet. This results into two problems:

  1. The content change event is triggered after closing each dialog.
  2. The tree is trying to select the item which doesn't exist yet. This results in a bug when adding a node at the root level since it tries to expand JCR root node (instead of the child which isn't saved yet) which is not part of the container.
    2016-04-29 09:43:21,969 WARN  agnolia.ui.workbench.tree.HierarchicalJcrContainer: Cannot determine parent for itemId: info.magnolia.ui.vaadin.integration.jcr.JcrNewNodeItemId@303012d2: javax.jcr.ItemNotFoundException: Root node doesn't have a parent
    


 Comments   
Comment by Mikaël Geljić [ 25/May/16 ]

Same warning observed on both tickets, though different scenario.

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