Error in install/update still allows Magnolia to startup (and thus most likely
fail miserably) when magnolia.update.auto is set to true
---------------------------------------------------------------------------------------------------------------------------------------
Key: MAGNOLIA-2445
URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-2445
Project: Magnolia
Issue Type: Bug
Components: core, updatemechanism
Affects Versions: 3.6.3
Reporter: Gregory Joseph
Assignee: Philipp Bracher
Fix For: 3.7
The exception handling is different depending on which ModuleManagerUI is used
(in ModuleManagerNullUI, everything happens in onStartup(), which is called in
ConfigLoader, while in ModuleManagerWebUI, everything happens in calls to
execute(), which are called by the InstallFilter)
In both cases, Magnolia should not start if the install or update was
unsuccessful. We only need to figure out what to with incoming http requests,
when using ModuleManagerNullUI. This is very much related to MAGNOLIA-2244
which asks for a review/cleanup/removal of the ConfigLoader.isBootstrapping(),
.isConfigured() and .enterListeningMode() methods !
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
----------------------------------------------------------------
