Update mechanism improvements
(MAGNOLIA-5529)
|
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | modulemechanism, updatemechanism |
| Affects Version/s: | 4.4.2 |
| Fix Version/s: | None |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
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. |
| Comments |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |