[ http://jira.magnolia.info/browse/MAGNOLIA-1373?page=comments#action_13668 ] Grégory Joseph commented on MAGNOLIA-1373: ------------------------------------------
Fabrizio, I also thought bootstrapping modules before loading xml files in the user bootstrap dir could help, but that would be awkward for modules you install on an existing system (since those would be bootstrap "after" the webapp bootstrap directories, obviously), so depending on how/when the modules would be installed, you would get different reactions from the system. I think generally the bootstrapping mechanism could use some cleaning up and simplification. Maybe adding stricter rules like "modules can only bootstrap content under their own node", although I'm sure you guys will come up with scenarios where this is not acceptable .. ;) > User configuration should have priority on module default config when > bootstrapping > ----------------------------------------------------------------------------------- > > Key: MAGNOLIA-1373 > URL: http://jira.magnolia.info/browse/MAGNOLIA-1373 > Project: Magnolia > Issue Type: Bug > Affects Versions: 3.0.1 > Reporter: Fabrizio Giustina > Assigned To: Boris Kraft > Priority: Blocker > > The current bootstrapping sequence don't let users change many default values > loaded by modules. > Bootstrap XML in modules is intended as a default, that should be loaded when > no other configuration is found and that could be overwritten by specific > configuration by users. > At this moment anyway modules configuration is loaded after user content in > the bootstrap dir and overwrites any custom configuration. I have several use > cases that were used to work with pre-3.0 builds and that now I can't make > work with 3.0.1, such as: > - adding custom mime-types: the whole server/MimeTypes tree is overwritten by > the late bootstrap of the adminInterface and new mime types are deleted. This > is also traced in MAGNOLIA-1353 > - changing cache configuration: the configuration in the cache module > bootstrap is definitively just a default since you should be able to choose > between different implementation. Also the cache filter in the server section > should be overwritable (by supplying a custom extension). None of these > configurations can now be changed at bootstrap, since at the end of the > bootstrap you will always end up with the module defaults. > What about bootstrapping modules before loading xml files in the user > bootstrap dir? Do anybody see problems with this or has an idea for a better > solution? -- 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://www.magnolia.info/en/developer.html ----------------------------------------------------------------
