[MAGNOLIA-6379] Changing properties of a JCR based definition triggers repopulation of all templates Created: 17/Sep/15  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia
Component/s: node2bean
Affects Version/s: 5.4.2
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-6521 Module config via Light Module 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   

The way to see the issue is to turn on DEBUG for info.magnolia.jcr.node2bean.impl.Node2BeanTransformerImpl. Next make a change to a template definition and observe log. Every change made to a template definition triggers the repopulation of every definition. Seems inefficient and could have impacts on performance when developing templates.



 Comments   
Comment by Roman Kovařík [ 31/Jan/19 ]

The JCR configuration is nowadays obsolete in favour of YAML (which doesn't suffer this issue).

If still needed in future, ModuleJcrConfigurationSource introduced with MAGNOLIA-6521 goes into the direction of reloading just the changed definition and part of the solution might be usable globally.

Comment by Richard Gange [ 09/Mar/21 ]

See MAGNOLIA-6521

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