[MGNLUI-6213] JcrNodeResolver fails when app has subapps with different datasources Created: 16/Sep/20  Updated: 22/Sep/20  Resolved: 18/Sep/20

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

Type: Bug Priority: Neutral
Reporter: Roman Kovařík Assignee: Adam Siska
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 0.2h
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLUI-5346 Migrate Security app to new framework... 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
Epic Link: Migrate apps to new UI framework
Sprint: UI FW 11
Story Points: 2

 Description   

Steps to reproduce

  1. Configure an app with different datasources (or use dam app or future security app)
  2. Select an item in non JCR datasource.
  3. Switch to subapp with JCR datasource

Expected results

No exceptions.

Actual results

JcrNodeResolver tries to convert ID from non JCR datasource to node, failing with an exception (red banner, no need to go to logs).

Workaround

App still works.

Development notes


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