Pierre van Rooden wrote: > Doe anyone know what sun conventions are for resource packages? > Should resource files be stored in org/mmbase/config or mmbase/config?
Perhaps even WEB-INF/classes/mmbase (without the config), what else then config would there be? Actually I was inspired by oscache, of which the config file can (must?) be placed in WEB-INF/classes/oscache.properties. The 'classes' directory is still a bit awkward, but non-java-programmers are perhaps a bit more baffled by WEB-INF/classes/org/mmbase/config > I am ok in storing config in another place than the class files, but I > would like to follow conventions were possible. Yes, I agree. I am also ok with WEB-INF/classes/org/mmbase/config, but I want to make a point of it. > > - Reading of web.xml of MMBaseServlet will not be possible any-more. It > > currently gives an > > stack-trace in my log, (but mmbase starts oterwise correctly). It is > > only used for that silly > > function to servlet mapping. I'm sure we can come up with some solution > > (if needed, by a copy of > > web.xml under WEB-INF/classes...) > > Yech. > No way to load it as as resource then? I'm not sure, but I'm pretty sure that we looked into that back then. Of course it is relatively stupid that the XML is parsed in the first places (there seem to be no methods to ask 'which servlets are in use'?, 'what are their mappings?'). > Otherwise we may need to move this type of configuration? Yes. Or perhaps we could apply some XML-hackery (entities?...). I hear the new yech's already... Michiel -- Michiel Meeuwissen mihxil' Mediacentrum 140 H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US
