[MAGNOLIA-1823] installation: 500 after installation Created: 08/Nov/07  Updated: 23/Jan/13  Resolved: 08/Nov/07

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 3.5 RC1

Type: Bug Priority: Blocker
Reporter: Philipp Bärfuss Assignee: Philipp Bärfuss
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-1671 Review the Server and Listener(ip con... 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
Date of First Response:

 Description   

The Server config object is not ready at that moment --> causes a 500

Not yet sure why. The repository is bootstrapped after the installation.



 Comments   
Comment by Philipp Bracher [ 08/Nov/07 ]

When the first attempt to read the configuration node fails in the ObservedFactory, the observation is not registered and the object will never be created later on.

Comment by Magnolia International [ 08/Nov/07 ]

"better" fix:

  • split ServerConfiguration out of Server
  • Install / ModuleManagerWebUI now uses a customized instance of FreemarkerHelp which doesn't rely on magnolia components (since they're likely to not be ready yet)
Generated at Mon Feb 12 03:30:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.