On Wed, 2002-10-02 at 10:41, Michiel Meeuwissen wrote: > I would say: lets keep things simple. Fetching 'resource' can be easily done > with the ClassLoader, and I don't feel like overriding anything there to > make it possible to put resources in WEB-INF/myapplicions or somethings like > that. Please simply put them in WEB-INF/classes/nl/omroep/myapplications and > everything goes all right. As someone who knows how resources work, i say you are right. As someone who looks at an system not knowing how java/mmbase works(a webdesigner) it would be a lot easier if you could put it inside an other directory (instead of creating a directory classes/org/mmbase/resources/xslt)
> > Of course we can make a fall back machanism with abritrary directories in > WEB_INF (simply opened as files), but I think having simply one (using mmbase > config directory) is complicated enough. Well, since you have to put this check in MMBase (to keep it backwards compatible), why not make it configurable? You have to say if not here, than look there in your code. Can you tell me where you see complications putting this order into a config-file instead of hard-coding it in MMBase? > IMHO using resources is more than acute enough to distinguish private, > third-party and mmbase resources. I dont like to place my xslt's in let's say: 'WEB-INF/classes/nl/omroep/myapplication/xslt', i think that WEB-INF/myapplicaltion/xslt or even WEB-INF/xslt would be much better to understand for someone who has to change the xslt's. Furthermore i think that org/mmbase/resources/ is a good location to place the resource files inside the war. -- Eduard Witteveen Systeem Ontwikkelaar Publieke Omroep, Gateway C Kamer 101 +31(0)356772910 http://www.omroep.nl/ Sed quis custodiet ipsos custodes? : The sixth Satire from Juvenal
