-
Sub-task
-
Resolution: Won't Do
-
Major
-
None
-
4.4.2
-
None
If a info.magnolia.module.ModuleLifecycle#start fails (with a RuntimeException of sorts), for instance because of a wrong configuration, the module should either be observed (so configuration can be fixed), or at least stopped (because some processes might have started). Or both?
Likewise, if c2b fails to initialize the module bean, it seems it's consequently not observed, so one can't fix the configuration without restarting.
- is related to
-
MAGNOLIA-3457 Config reload on Module doesn't work if config-node is missing at start.
- Closed