A few days ago another related discussion took place, and Philipp suggested in order of preference, the following solutions:
[quote] A) The best solution I can see is that one can define in the import a folder. Then you haven't to import multiple files. This means that you can bootstrap when ever you like. A flexible mechanism is the with 3.0 delivered packaging mechanism (you select pathes you like to export) This could be done easily since all the methods are already written. Perhaps one should be able to zip multiple files into one. B) post-bootstrap I don't like this idea but it is near the solution we had before. We could have a directory like the bootstrap containing files loaded after the registration of the modules. C) module does not overwrite already existing pathes in the repository. I prefer A) since this is how other system are working. [/quote] and the main reasons for this: [quote] - In my opinion a module is something independent and it is necessary that a module can install itself without someone changing it's configuration in advance. - this enables a proper uninstall since the modules defines it's servlet, repository, configured pathes in the config [/quote] On 4/2/06, Alexandru Popescu <[email protected]> wrote: > Hi! > > I've been thinking a lot after our last discussions about how would it > be possible to customize the modules, without needing to change the > modules or going manually over them. > > Currently, the first conf files are imported from WEB-INF/bootstrap > dir. Later on the process, the module is overridding these (if it is > the case): > > [code: ModuleUtil lines: 145-148] > if (hm.isExist(fullPath)) { > hm.delete(fullPath); > log.warn("already existing node [{}] deleted", fullPath); > } > [/code] > > I guess a better approach would be to have the mechanism work in the other > way: > > if the conf is already defined, it means that the admin customized the > system when the system first bootstrap, and so the module conf should > not override it. > > The change to support this behavior is quite trivial and IMO the > system would be easier to be configured from the pov of sys admins. > > What do you think about this idea? > > ./alex > -- > .w( the_mindstorm )p. > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
