[ http://jira.magnolia.info/browse/MAGNOLIA-1853?page=comments#action_15118 ] Philipp Bracher commented on MAGNOLIA-1853: -------------------------------------------
>The "pre-startup" phase also sounds reasonable, but I'm afraid we'll need a >pre-pre-startup phase, a post-startup phase and so on and so forth. I look at it as something similar to running level on unix systems. Having this phases (I still would like to have them for installation too) allows very flexible startup scenarios. Here is a kind of draft example (a bit too many extra phases indeed): 1: the repositories/namespaces are regesitered 2: nodetypes are registered 3: core starts for example a to-be-observed registration 4: ... 5: start observation, other daemons, .. What I would like to see is that the ConfigLoader disapeares and is completely mapped into this startup level thingy We might then use the same kind of levels for installation by putting the system in a certain runlevel > ModuleLifecycle : allow usage of the Task api and global save/rollback > ---------------------------------------------------------------------- > > Key: MAGNOLIA-1853 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1853 > Project: Magnolia > Issue Type: Task > Components: core > Reporter: Grégory Joseph > Assigned To: Grégory Joseph > Fix For: Green > > > This is currently implemented through startupTasks, but using the > ModuleLifecycle is more relevant, since startup tasks are not related to any > given version of a module -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia.info/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
