Rob van Maris wrote: > Over the past years I have helped a significant number of java > developers to get started with MMBase. One thing I noticed is that > understanding the configuration is made a lot easier by the fact that > all configuration files reside in one location, i.e. WEB-INF/config. > If we introduce a set of default config files in an entirely different > location (i.e. in the classpath), the opposite will be achieved, making > it hard to understand the configuration. > > Perhaps all this isn't a problem to the commiters on this mailinglist. > But for most developers it will be very confusing.
I do understand what you mean, therefore I'm not very in favour of copying _all_ config's to mmbase.jar, but there are two things which make the situation less confusing: - The location in the jar is precisely the same (only prefixed by org.mmbase). So you only have to know that this is so, and jar tf mmbase.jar | grep org.mmbase.config will illuminate you. It will also work for any config file on the same way. Exceptions will be abolished (such as there were 'taglibcontent.xml', 'databases/*.xml' and a few more). Exceptions always contribute to confusion, of course. - There is a 'resoureeditor' available, in the admin-pages, which shows excactly where a certain resource is loaded from and can be loaded from. This tool will immediately solve any confusion. At least, so I hope. This is of course under the assumption that beginners familiarize themselves a bit with the admin-pages. Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [EMAIL PROTECTED] http://lists.mmbase.org/mailman/listinfo/developers
