Loading...

XML

Word

Printable

Type: Improvement
Resolution: Fixed
Priority: Major
Fix Version/s: 4.1
Affects Version/s: 4.0.1
Component/s: updatemechanism
Labels:
None

Template:
Acceptance criteria:

Empty

show more show less
Task DoD:

show more show less

Since FactoryUtil.newInstance() is re-throwing exceptions (~~MAGNOLIA-2552~~) a module or component startup can fail.
ModuleManager and Content2Bean itself should be aware of this and treat exceptions accordingly.

Acceptance criteria

is related to

MAGNOLIA-2445 Error in install/update still allows Magnolia to startup (and thus most likely fail miserably) when magnolia.update.auto is set to true

Closed

MAGNOLIA-2552 FactoryUtil: newInstance() method should throw an exception and not return null if the object can't be instantiated

Closed

MAGNOLIA-2598 Module dependency issue should be displayed in update ui

Closed

MAGNOLIA-2711 Failure to resolve class when finishing installation leads to 404 page being displayed after installation

Closed

is superseded by

MAGNOLIA-1670 Updatemech : review exception handling (loading and lifecycle)

Closed

Assignee:: Philipp Bärfuss

Reporter:: Philipp Bärfuss

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 25/May/09 12:21 PM

Updated:: 23/Jan/13 9:09 AM

Resolved:: 15/Jun/09 2:31 PM

Date of First Response:: 25/May/09 4:22 PM

Task DoD

Details

Description

Checklists

Attachments

Issue Links

Activity

People

Dates

Checklists