[MAGNOLIA-2743] startup: don't fail to start the system just because a single module/component fails to start Created: 25/May/09 Updated: 23/Jan/13 Resolved: 15/Jun/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | updatemechanism |
| Affects Version/s: | 4.0.1 |
| Fix Version/s: | 4.1 |
| Type: | Improvement | Priority: | Major |
| 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: |
|
||||||||||||||||||||||||||||
| 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 |
|
Since FactoryUtil.newInstance() is re-throwing exceptions ( |
| Comments |
| Comment by Philipp Bärfuss [ 25/May/09 ] |
|
Since FactoryUtil.newInstance() is re-throwing exceptions a module or component startup can fail. Various places must be made aware of that fact:
|
| Comment by Magnolia International [ 25/May/09 ] |
|
|
| Comment by Philipp Bärfuss [ 25/May/09 ] |
|
The problem I run into is that the system was miss configured (well by some install tasks but the install did not fail at all). That went as far as that a single miss configured command stopped the system to start up. |
| Comment by Magnolia International [ 29/May/09 ] |
|
Partly fixed in 4.1 RC1; will review before final - and either leave as it or push the issue to 4.1.1 if needed. |