[MGNLCE-68] Tests fixture module create /templates/components folder with wrong nodeType causing node2bean problems with template definitions Created: 21/Dec/16  Updated: 04/Jan/17  Resolved: 21/Dec/16

Status: Closed
Project: Community Edition
Component/s: None
Affects Version/s: 5.5
Fix Version/s: 5.5.1

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

Issue Links:
Relates
relates to MGNLCE-70 Integration tests fixture module is s... 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: Definitions app problems
Sprint: Basel 75
Story Points: 1

 Description   

Component templates components node has nodeType mgnl:contentNode causing Node2Bean to interpret that node as template, resulting in the following error in the problems app:

template: test:components (from jcr at /modules/test/templates/components)

Source data processing problem Property [test_jsp] not found in class [info.magnolia.rendering.template.configured.ConfiguredTemplateDefinition], property is not assigned /

Source data processing problem Property [test_ftl] not found in class [info.magnolia.rendering.template.configured.ConfiguredTemplateDefinition], property is not assigned /

Source of the problem

The source is an erroneous NodeBuilder task which creates the components folder on the wrong level, resulting in info.magnolia.module.delta.PropertiesImportTask creating the non-existing folder with the wrong nodeType.

Once the addNode task is "moved" inside the parent's node addNode task, the error is gone.

How to reproduce

Simply run the the CE bundle in manual test mode and see problems tab of definitions app: e.g. mvn clean install -P manual-tests,jetty9-standalone.


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