Kees Jongenburger wrote: > > An alternate possibility is to move the 'core' config (core builders, > > stoarage ersoyrces, dtds, basic default configuration xmls) into the src > > tree, and instead of copying the config to the jar, copy the contents of > > org.mmbase.config to the config dir. > It is very unlikely that any real mmbase app will not have it's own > WEB-INF/config directory. it's not called config by hazard :) > Having the resources and dtd's in the src tree was a bad idea in the > first place. worse is if like now we have both resources configs all > over the place for no apparent reason (other than making it difficult > to find dtd's and validate xml's)
I think dtd's are actually another issue, because those are not configuration. According to me, there is no way you could ever want to change a DTD, because there should be a 1-1 relations between DTD and implementation. So, it would make sense that dtd's are not found in the config-dir. 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
