[MAGNOLIA-1327] ModuleUtil.bootstrap() uselessly creating nodes before import, and in the wrong workspace Created: 31/Jan/07  Updated: 23/Jan/13  Resolved: 31/Jan/07

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 3.0.1
Fix Version/s: 3.0.2, 3.1 M1

Type: Bug Priority: Critical
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-1326 ModuleUtil.bootstrap() could accident... 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

 Description   

In ModuleUtil.bootstrap(), we try to create the parent of to-be-imported nodes before delegating to the actual import code (DataTransporter.importXmlStream), but
1- this is always done in the "config" repository (same bug as MAGNOLIA-1326)
2- not visible since done in the system session, which happens to be never same afterwards in most cases *

this is useless since DataTransporter.importXmlStream does it (and in the correct repository this time!)

  • It only becomes visible if by chance, after bootstrapping nodes outside the config repository, another module bootstrap files again in the config repository, and thus saves it.


 Comments   
Comment by Magnolia International [ 31/Jan/07 ]

fixed in 3.0 branch and trunk

Generated at Mon Feb 12 03:25:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.